IDoc split ADRMAS+DEBMAS

Hi ,
I am trying to do the ADRMAS+DEBMAS split .I doing it for the first time.
Do i need to configure any thing in ECC apart from partner profile.
Is there any documentation on how to do the split from DEBMDM in XI and what to configure in ECC.
Please guide me.
Thanks and Kind Regards,
Basheer

Hi Basheer,
Please let me know your E-mail id, so that I can send a document to configure in ECC as well as you can use XI standard content for MDM for configuration in XI. so SAP has already designed XI content just you need to configure that.
Hope it will helps you.
Regards,
RDNPrasad.
Edited by: RDNPrasad on Jun 26, 2008 6:39 AM

Similar Messages

IDoc Split to different IDocs!!!!!!!!URJENT

Hi
Is there any possibility to split the IDoc ?
We have a scenario like - Header without any data - Segments with the data - trailer segment with the details of the segment count and parent idoc details.
We received one Inbound IDoc with 20000 segments.
While processing the IDoc, because of the huge data it is going to dump with low memory issue.
Is there any possiblity to split the segments into seperate idocs...in WE19 we can cut down the segments and create seperate idoc but count is very high we are not able to identify the numbers count.
Is there any other way we can process the IDoc splitting into different IDocs.
VVR
FICO Consultant

Hi Vuppala,
CAn you please help how u split the IDOC.
I have ARTMAS IDOC and as there is huge data i need to split it.
Can you please help
Thanks,
Akriti

Why customer master idoc named like DEBMAS?

hi,
i am just curious know why customer master idoc named like DEBMAS?
vendor master data idoc as cremas?
any German abbreviation or English abbreviation behind this will be appreciated.
thanks & regards
Raja
Message was edited by:
Raja

To my knowledge I do not think that the naming has anything to do with the German translations since in German:
Customer = Kunde and
Vendor = Verkäufer....
However the naming has some connection with the Business Case behind customers and vendors. In SAP, a customer is a business partner whose account you debit for money, hence the name DEBMAS and a vendor is a business partner whose account you credit money, hence the name CREMAS.
PS: Reward points and close the question if you find this helpful.
Regards.

Idoc split program

hi,
what is the use of idoc split program.in which scenario it will be used?
Ganesh

Spliting the idoc - suppose you have purchase order - when you create purchase order then it will create one idoc.
some times requirement would be like - purchase order has many line items ,clients need each line item as one idoc ,here we need create multiple idoc for one order ( For this we need to change the logic with in function module)
Reward Points if it is helpful
Thanks
Seshu

Inbound ECC, ADRMAS/DEBMAS Processing with Customer # Assignment

I am looking for someone with recommendations on how we can get ADRMAS and DEBMAS IDocs transformed with new customer number and processed in proper order in ECC. The IDocs are being sent from a hub MDG system with a hub customer number in them. They get sent over via ALE to the destination ECC system and we have them set to not process immediate. We plan to process them via a program that needs to look up the next available customer number on the ECC (using internal number assignment) and process both IDocs with the new ECC customer number.
We need to coordinate the ADRMAS processing before its' respective DEBMAS.
Any suggestions are appreciated.
Thank you,
Keith

Hi Keith,
You might want to consider using "Serialization by Message Type" in the receiving system.
Please refer to below link which has more information :
Serialization of Messages - ABAP Development - SCN Wiki
Also, if you have internal number assignment for the customer, the system will propose a new available customer number.
Thanks,
Kumaran

Delivery IDOC Split

Issue:
We could observe that the error coming in the Idoc XXX; are errors involving the financial postings that occur as a result of the inventory movement associated with a goods issue.
Error Message:
Maximum number of items in FI reached
The above error in IDOC is due to max. number of items for an FI Document(999) is exceeded.
As per my understanding, I think we have to split the delivery document into two parts and post to FI accordingly
As FI documents is getting posted through IDOC, how can I limit my IDOC to process just 50% of line items(How to split my Delivery though IDOC)

Refer below note:
Note 1353827 - AC interface: Document split in FI for goods movements
Regards
Sreenivas

INBOUND DELFOR02 Idoc Split

Hi,
I got a requirement for an inbound idoc
Idoc type : DELFOR02
message type : DELINS
User exit functional module : IDOC_INPUT_DELINS
My actual reqirement is.......
The DELFOR02 Idoc sent from the subsystem to SAP will have to be split into multiple DELFOR02 Idocs depending upon the number of line items.
The DELFOR02 Idoc is separated into header and item data. The header data will have to be mapped to each split Idoc and then update each Scheduling agreement. The Item detail will have to be split for each occurrence of an E1EDP10 segment. For example if 3 line items are contained on the DELFOR02 Idoc this will have to be split in to 3 Idocs, as shown below:
DELFOR02 Idoc
Header Level          E1EDK09
Item Level                    E1EDP10
                              E1EDP10
                              E1EDP10
How i approach this requirement.......please help me out..its critical req

Hi,
I am just briefing the steps on how you can proceed. The following information may not be complete.
Copy the functional module : IDOC_INPUT_DELINS to new custom FM Z_IDOC_INPUT_DELINS and link this to existing process code.
In FM Z_IDOC_INPUT_DELINS :
store the header data into global structure, also populate T_NEW_IDOCDATA.
Then based on your conditions, i.e. no of segments E1EDP10
case IDOC-SEGNAM.
when 'E1EDP10'.
store the segment data into internal table T_NEW_IDOCDATA.
perform create_new_split_idoc.
endcase.
FORM CREATE_NEW_IDOC.
MOVE-CORRESPONDING IDOC_CONTRL TO S_CONTROL_RECORD_IN.
S_CONTROL_RECORD_IN-MESCOD = 'SPT'.   "new message code SPT for split Idocs
S_CONTROL_RECORD_IN-DOCNUM = SPACE.
S_CONTROL_RECORD_IN-IDOCTYP = IDOC_CONTRL-IDOCTP.
APPEND S_CONTROL_RECORD_IN.
CALL FUNCTION 'INBOUND_IDOC_PROCESS'
     TABLES
          IDOC_CONTROL = S_CONTROL_RECORD_IN
          IDOC_DATA    = T_NEW_IDOCDATA
     EXCEPTIONS
          OTHERS       = 1.
   IF SY-SUBRC = 0.
COMMIT WORK.
endif.
ENDFORM.
For split Idocs create a new message code SPT and do the partner profile setting in WE20.
Thanks,
Savitha

ORDERS Idoc splitting into two

Hi,
   I have requiremnt where i need to Split Orders idoc into messages.
   1. Orders XML file 2.XML file only with control record fields.
i have seen all the discssion on this and deceiced to implement the scenario as per
/people/jin.shin/blog/2006/02/07/multi-mapping-without-bpm--yes-it146s-possible   blog. But the problem is need to use two message types on the target side.. for splitting the message..
ORDERS and Contrlo record Fields message type... i can't change the standard idoc..
Can i add the Control record fields to Standard IDOC in any way....   like exporting file...if so..
tell me whether the Idoc will split into two messaged or not....
Regards,
Deep

My doubt is in the mentioned blog target msg type was created one.. here i need to take with ORDERS idoc(ED in our case). I need to split the IDOC everytime when it triggers based on RCVPRN field value.. this value is always so there should be 2 values everytime.
you will need to duplicate the IDOC at the target side to achieve this...if you are successful in doing the 0...unbounded thing for your IDOC....
1) Duplicating:
Duplicating is not Multimapping.....Multimapping is what you saw in the blog and duplicating is right-clicking on the node and choosing Duplicate Subtree....no two messages will be created in this process (duplicating).....
2) Multimapping:
it is used to create two (or more) different messages at the target end...
Does it split into two message ( ORDERS XML and Control Record XML)
No it wont split the IDOC into two messages.....
So if your requirement is to have only one target message with seperate IDOC nodes..having ORDERS and Control data individually...then go for duplication method...apply the condition for RCVPRN to generate the nodes...
If your req is to have two different messages at the target then use multimapping apply the condition for RCVPRN to generate the two different messages.....
Hope it helps...
Regards,
Abhishek.

IDoc Split with out BPM using SplitByValue at the LineItem Level

I have an Invoice idoc contains line item and identifier changes into groups, let's say A & B
Using Message Mapping, Will i be able to Split into 2 IDOCs and combine A into one IDOC and B into Another IDOC and send it across to ECC with out using BPM?
Btw the header is commom for both the IDOCs
Source
<Header>
<headertext>headername</headertext>
<lineItem>
<item1>A</item1>
<item2>B</item2>
<item3>A</item3>
<item3>B</item4>
</item>
</lineitem>
</header>
Target
IDOC 1
<Header>
<headertext>headername</headertext>
<lineItem>
<item1>A</item1>
<item2>A</item2>
</item>
</lineitem>
</header>
IDOC 2
<Header>
<headertext>headername</headertext>
<lineItem>
<item1>B</item1>
<item2>B</item2>
</item>
</lineitem>
</header>
Any inputs are appreciated

I actually gave wrong information on the source structure, I am trying to execute scenario with the given examples, meanwhile any help is appreciated
<Header>
               <Date>20100112</Date>
               <Amount>10</Amount>
               <No>20</No>
</Header>
            <InvoiceItem>
               <Line1>10</Line1>
               <Line2>10</Line2>
               <Amount>10</Amount>
               <ActionIndicator>I</ActionIndicator>
            </InvoiceItem>
            <InvoiceItem>
               <Line1>20</Line1>
               <Line2>20</Line2>
               <Amount>20</Amount>
               <ActionIndicator>C</ActionIndicator>
            </InvoiceItem>
            <InvoiceItem>
               <Line1>30</Line1>
               <Line2>30</Line2>
               <Amount>30</Amount>
               <ActionIndicator>I</ActionIndicator>
            </InvoiceItem>
            <InvoiceItem>
               <Line1>40</Line1>
               <Line2>40</Line2>
               <Amount>40</Amount>
               <ActionIndicator>C</ActionIndicator>
            </InvoiceItem>
Target 1
<Header>
               <Date>20100112</Date>
               <Amount>10</Amount>
               <tNo>20</No>
               <ActionIndicator>I</ActionIndicator>
</Header>
               <InvoiceItem>
               <Line1>10</Line1>
               <Line2>10</Line2>
               <Amount>10</Amount>
            </InvoiceItem>
            <InvoiceItem>
               <Line1>30</Line1>
               <Line2>30</Line2>
               <Amount>30</Amount>
            </InvoiceItem>
Target 2
<Header>
               <Date>20100112</Date>
               <Amount>10</Amount>
               <tNo>20</No>
               <ActionIndicator>I</ActionIndicator>
</Header>
               <InvoiceItem>
               <Line1>20</Line1>
               <Line2>20</Line2>
               <Amount>20</Amount>
            </InvoiceItem>
            <InvoiceItem>
               <Line1>40</Line1>
               <Line2>40</Line2>
               <Amount>40</Amount>
            </InvoiceItem>
I know the part of Splitting IDOC, which was executing correctly, with the external data type changes. Please advice

IDOC Splitting

Folks,
I have a iDOC - to - iDOC scenario where i need to split an idoc on receiving side without using BPM. Can anybody please tell me how to do it . We are running on SP14
Manish

Hello Manish,
no, thats all.
The Interfacemapping is the same.
But please check in the mapping that you build a mapping on the UNBOUNDED segment now. But I think you have done that.
Just for understanding:
This mapping will not create singel IDOCs in XI, this will create an IDOC package and this IDOC package is sent through the IDOC adapter then.
In your R/3 system you will get single IDOCs then.
best regards
Werner

IDOC Filtering for DEBMAS

I am currently using change pointers to trigger the DEBMAS IDOC. I need to be able to filter a range of customers that are not required to be sent. These customers have a defined class type, so it would be ideal to prevent these from going through with a <> filter.
I'm looking into the Distribution Model filter, but the options appear limited to Function, Company Code, Credit COntrol Area, Division, Sales Org, Dist Chnl.
Any ideas to exclude this type of customer from the IDOCs being processed would be very much appreciated.
Thank you!
Jaime

Hi,
Using BAPI, you can filterout the customers that not required to process thru ALE.
Filters are conditions that BAPIs have to satisfy so that they can be distributed by ALE outbound processing.
The BAPIs and message types in a model view that are filtered contain a relevant sub-entry.
In the change mode you can define filter groups and values by selecting
Edit -> Display/edit details.
The following types of filtering are possible:
Data Filtering with BAPIs
Prerequisite:
You have defined the filter objects for a specific BAPI and assigned them to the BAPI. For more information see the ALE Programming Guide under Filtering Data.
There are two types of filtering to choose from:
Interface Reduction:
Here optional BAPI parameters and/or BAPI fields are switched off.
You can choose the options:
- Reduce by fields
- Fully reduced
For example, the BAPI RetailMaterial.Clone is called with parameters containing basic data, production data, sales and distribution data, plant data, etc.
If the BAPI is called by a material reference system in a sales and distribution system, only the parameters containing basic data and sales and distribution data have to be transferred.
Content-Dependent Filtering
The rows of the BAPI table parameters which do not satisfy the distribution conditions are filtered out.
Developers can also use field references to define hierarchy relationships between table parameters. Such hierarchies are maintained in the ALE Development menu under BAPI -> Maintain hierarchy for BAPI table parameters.
For furhter details please click on below link:
http://help.sap.com/saphelp_46c/helpdata/en/4f/1c4b6e5733d1118b3f0060b03ca329/frameset.htm
You may try with this info.
Thanks,
Naga

Idoc Split

Hi,
I have a scenario in which the invoice idoc's coming out of R/3 are being routed for a set of customers via XI(with some transformations in XI) and others are routed to a 3rd party.
My question is invoic01 idocs need to identify based on customer details and go correspondingly to XI or the 3rd party. eg: 12 customers are set to receive invoice through XI. How is it possible to send the invoice to these 12 customers Via XI based on the invoice idoc created in R/3? Mostly its like segregating the invoice idocs based on customers through XI and the rest to the 3rd party.
Any help would be highly appreciated.
-Teresa

I think that you mean that you do not even want to receive the IDocs in XI if they are not the 12 customers that should be routed there? If this is the case, I would sugest setting up 2 output types for invoices in Output Determination inside R/3. Have one of them point to XI, the other one to the 3rd party product. On the XI output, set up a requirement on the output procedure to select whatever criteria it is and only trigger the output if the criteria is met. On the other output type only trigger the output if the criteria is not met. This way you can filter them out before ever getting into XI.

File to multiple IDOC split without BPM

Hi expert,
I have a flat file to IDOC scenario. In flat file, I have thousands of rows. Each row need to create one IDOC. In IDOC, I have 3 segments(seg2 is the child of seg1, seg3 is the child of seg2). Each field in flat file will be mapped to the same name in IDOC. Here is my example structure:
MT_Flatfile
row--0:unbounded
seg1a --0:1
seg1b --0:1
seg2a - 0:1
seg2b - 0:1
seg3a - 0:1
seg3b - 0:1
Sample_IDOC_name
IDOC - 0:unbounded
EDI_DC40
seg1 - 1:1
    seg1a - 0:1
    seg1b - 0:1
    seg2 - 0:unbounded
      seg2a - 0:1
      seg2b - 0:2
      seg3 - 0:unbounded
      seg3a - 0:1
      seg3b - 0:1
I mapped row to IDOC. It did create multiple IDOCs. But each IDOC only contain seg1. Then I mapped row to seg2 and seg3 node. The first IDOC has three segments and the rest still only have seg1. And in first IDOC, the seg1 is filled correct. seg2 and seg3 have multiple records. Can anyone tell me how I do mapping without using BPM for this case to make each IDOC has one seg1, one seg2 and one seg3?
Thanks a lot.
Charles
Edited by: Charles M Gates on Nov 22, 2011 4:08 PM
Edited by: Charles M Gates on Nov 22, 2011 4:09 PM

Hi,
Your issue come from certainly to the fact that in source file, for at least one row, there is a segN which is missing (see occurence "0..1").
And so after that, you have a bad behavior to the target Idoc segment, due to the fact you did not manage properly the Context. In Message Mapping, use the right click to display your context, and you will see a difference of context between your source and the desired target.
the error certainly appears for a sub-segment which exist whereas its highest level is missing (in your source).
regards
Mickael

One IDOC split to multiple IDOC's

Scenario is in ECC 6.0 and SAP PI 7.0 .
SAP is sending Custom IDOC to PI 7 and PI 7 is sending that to receiver system.
The custom IDOC sometimes contains more than 250 segments and receiver system is not able to process IDOC's with more than 250 segments. Receiver system is having this limitation.
QNS :
(1) What are options to restrict IDOC's creation to 250 segments in SAP
OR
(2) Can it be taken care at SAP PI 7.0 end. Like 1 doc is coming to PI with more than 250 segments and Can PI break this into multiple idoc's of max 250 segment length so that no data loss is there.
Your suggestions are needed for both options.
Thanks in advance..

Try out this mapping-
You need use 1:n mapping by making the occurance of target MT to unbounded.
Idoc -> Index(context,increment1)-> Division by n(250)->floor->SplitByValue->collapseContext->TargetMT
Segment ->Index(context,increment1)-> Division by n(250)->floor->SplitByValue->Target Segment
Iam not sure on how to build this logic in SAP.But the effective way is to implement this restriction in SAP before IDoc reaching PI.

Change IDoc Split Threshold

Hi,
when I run transaction PFAL with message type HRMD_A and basic type HRMD_A05, I find that new IDocs are created when the number of segments exceed 400. I would like to increase that number. How can I achieve that?
Thanks.
/ Elvez

Hi!
You should have a look at transaction <b>WE20</b> (partner profiles), look for the pp that is used in this IDoc scenario, then double click on output message type, and in tab <b>Outbound Options</b> you should see the value in field <b>Pack. size</b>.
Hope this helps - please reward me if it does.
Regards, Joerg

IDoc split ADRMAS+DEBMAS

Similar Messages

Maybe you are looking for