Skip to main content

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.

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: 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:


Popular posts from this blog

Raspberry Pi + svxlink = Low power echolink node

What is the easiest way to get echolink node up and running on raspberry pi? Surely, get a premade image which has everything inside. I've created one image which can fit into 2GB SD card for this, just follow the following steps to get it up and running:

For hardware, you need to have the following:
Raspberry Pi for sure, with a minimum 4GB SD cardA USB echolink interface, can be commercially sourced or DIY. There are many DIY schematics out there that you could follow.  Here is the configuration on how to get the things working together, courtesy of website:

For software:
Download the following prepared image from google drive, it is based on raspbian-2015-02-16 image and has pre-installed svxlink-14.08. raspi-wheezy-svxlink.img.zipUnzip the file and copy it to your SD card using the following instructions that can be found here.Boot up the RasPi, if you do not have an HDMI monitor, you may want to access the RasPi from your terminal emulator (putty or the like), connec…

Configuring TechniColor TG784N V3 (Maxis issued broadband router) to use different DNS servers

Previous write up deleted. It seems to change the DNS servers in as shown on the status, but it does not really work.

Check the following website, this seems to work:

This can be done from the WEB GUI too, go into the following configuration path:

In my example above, I'm using paid service unblock-us instead of google public DNS servers.

Debugging DMEE

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 few suggestion was to create a user exit just before the node that we would like to debug and put our breakpoint there. It seems that SAP has built-in this feature without needing us to create a user exit (available in ECC 6, have no idea if this is available on prior releases). Here is how you can put your breakpoint without any coding.

1. Display your DMEE tree using transaction: DMEE_DEBUG.

2. Click on the node that you would like to debug.
3. Go to conditions tab, you could see the Set Breakpoint button. Click to set.

4. Run the SAPFPAYM and specified the payment run date/id, payment format etc. SAP will stop at the node which you point your breakpoint at, as in 2.
5. To remove your breakpoint, just run the DMEE_DEBUG again, there is an option to delete all own breakpoints or all.