Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Reply from Zdeno on Nov 9 at 8:46 AM Sure, I can create Z_BAPI_RE_CN_CHANGE /...GET_DETAIL with SELECT Z-fields before BAPI...GET DETAIL and UPDATE Z-fields after BAPI...CHANGE. But I cannot believe there is no less stupid solution.
Thanks
Zdeno
| | | ---------------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. __.____._ |   _.____.__ |
