Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Reply from R. N. Wilhite on Nov 9 at 9:32 AM Have you checked for notes? That doesn't seem like an appropriate action from a BAPI. Neal
| | | ---------------Original Message--------------- From: Zdeno Sent: Friday, November 09, 2012 8:24 AM Subject: BAPI Deletes Z_Fields from Non CI_Includes BAPI_RE_CN_CHANGE can regularly handle customer fields in CI_DATA. Changed Contract contains also table of Conditions. The conditions have their Z-data in customer append of VICDCOND (some master data converted by migration from previous system). Whenever a condition of a contract is updated by the BAPI from my program, all Z-fields in master record of the condition are cleared. The standard transaction RECN doesn't do the error but it uses API_RE_CN_CHANGE. I'm not sure if it's the reason. How can I make BAPI to let the Z-fields unchanged? Is there a risk to use API instead of BAPI? | | Reply to this email to post your response. __.____._ | In the Spotlight Become a blogger at Toolbox.com and share your expertise with the community. Start today. _.____.__ |