BAPI_PO_CHANGE and 4.6C

Chatterjee, Partha (US - San Ramon) pchatterjee at deloitte.com
Mon Jun 7 15:49:07 EDT 2004


Hi Sri,
 
BAPI_PO_CHANGE is basically broken in 4.6C meaning various changes do
not occur as advertised.  At my last client, we worked with SAP
developers for 6+ months resolving various issues.  I would suggest that
you get that process started right away.  Make sure you are on the right
patch levels of course.
 
A couple of workarounds you may try:
 
1) create a BDC instead (I know its not recommended or supported)-- this
may work well if you are not changing any z-fields or fields specific to
the ME52N t-code.
 
2) instead of BAPI_TRANSACTION_COMMIT use 'commit work' with a command
like 'wait until 5 seconds'.  When we were going through various rounds
of testing, the wait command seemed to work until SAP broke something
new.
 
3) SAP basically backported the code for the 4.7 BAPI into 4.6C to start
fixing our problems.  That is something you may want your ABAPers to
explore on their own also.
 
Good luck,
 
Partha Chatterjee
Enterprise Applications
Deloitte Consulting LLP
 
Tel: +1 650 372 4594
Fax: +1 925 365 2170
Mobile: +1 310 701 1119
pchatterjee at deloitte.com
www.deloitte.com
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
Sri Neela
Sent: Monday, June 07, 2004 12:35 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: BAPI_PO_CHANGE and 4.6C
Importance: High
 
All,
 
Has anyone worked with BAPI_PO_CHANGE and R/3 4.6C and have a minute to
help me??
 
Scenario:
BAPI_PO_CHANGE and R/3 4.6C status is not released for customer in SWO1:
BUS2012
 
I am trying to use this BAPI to change PO line item Tax Code for ME22N,
but apparently not working.  Update is not happening with new tax code
by line item. Have used BAPI_Transaction_Commit to do the commit work
and wait.  Trying to see if anyone else has gone thru. similar
situtation or what steps we have to follow to use unreleased BAPI??
 
Below are some of the OSS notes from SAP, not sure what else I need to
do.. For this BAPI to work for my scenario.
577398    Enjoy PO BAPIs in SAP R/3 Release 4.6B
484692    BAPI_PO_CHANGE Delv. date not considdered
Release 4.6B according to note 197958.
 
Thanks in advance.
 
-Rgds,
Sri Neela
 
 
 
This message (including any attachments) contains confidential =
information intended for a specific individual and purpose, and is =
protected by law.  If you are not the intended recipient, you should =
delete this message.  Any disclosure, copying, or distribution of this =
message, or the taking of any action based on it, is strictly =
prohibited.
 


More information about the SAP-WUG mailing list