To get the multiple company codes to work, it seems that the sequence of segments in the CT_IDOC_DATA is important. I was reading the problem found here: http://scn.sap.com/thread/3257644 which says that someone had the same problem as me, "Fill all required fields " kind of error. It took me few hours replicating the sequence, trials and errors and found out that the sequence of segment in CT_IDOC_DATA is important. I couldn't get pass the error if I have the E1KNB1M segment (and it's child segments) earlier than the E1KNVVM segment. Moving the E1KNB1M segment to the end seems to solve my problem. So, if you've problem with your DEBMAS IDOC, trying to create multiple company codes for the customer, try move the segments around, best is to follow the sequence found in the DEBMAS which is:
Wednesday, 22 April 2015
SAP - Creating customer with multiple company codes using IDOC - Message type = DEBMAS
I had a hard time to make this thing working, replicating customer from CRM and extending the company codes to more than one. The standard CRM -> R/3 won't have a company code and some of the information available during the replication. However this can be added in few places, one of them is using BTE (transaction FIBF->Infosystem P/S), event DE_BALE. We can add our own entries into the CT_IDOC_DATA or manipulate the entries.
Subscribe to:
Post Comments (Atom)
TOUCHTAB report, regenerate all ABAPs related to changed/modified structure
I was working on S4HANA OnPremis and tried to do an enhancement to BP's additional info structure by appending fields, but decided that ...
-
Was looking for the best AC wifi router to replace my Buffalo WHR-G300NH and found that TP-Link has just released an Archer C7 V2 which has ...
-
I've come across many posting on the Internet (via google search), people asking on how to debug a DMEE for payment program. One of the ...
-
I've just subscribed to Astrill vpn service with a thought that they've openwrt scripting works as per the old twitter post that say...
No comments:
Post a Comment