Serialization group

what is serialization group?
how to create serialization group (using which T Code)?

Hi,
Check this link :
http://help.sap.com/saphelp_nw04/helpdata/en/0b/2a66e3507d11d18ee90000e8366fc2/content.htm
regards,
Sreevani

Similar Messages

Serialization Groups in Inbound Process

Can any one provide me the information about "How serialization Group" concept works in Inbound?
Thanks,
Sekhar.J

Hi Boss,
Serialization is nothing but sending the idocs in sequence.
Best Regards,
Narasimha Rao.

ALE Serialization

Hi All,
I want to do ALE serialization for IDOC coming for SAP XI. I tried to create serialization group but it is giving as 'Choose the key from the allowed namespace'.
What should i do?
Ranjeet Singh.

Hi Bhavesh,
Thanks for the reply. Actually i dont want to do idoc serialization in SAP XI. I want to do it in R3 side through ALE Master Data Distribution Serialization. We have interface between R3 and MDM and data is Customer master data. We want to send ADRMAS IDOC first and then DEBMAS data. Currently we are doing this using BPM with a 5 min wait betweeb sending IDOC. But since performance degrading approach, I am thinking of movng this logic to R3 side so that we dont; have to BPM adn wait step in XI and hence performance get improved.
Ranjeet Singh.

Serialization of IDocs

Hello friends,
I have one question pertaining to serialization:
Does serialization depends only on the order of message type maintained in serialization group. Is the content of the IDoc also taken into consideration during processing.
Eg. Say I have serialization of 2 Idocs - ORDERS and MATMAS
a) MATMAS first followed by ORDERS.
b) I send 4 IDocs:
         - MATMAS IDoc containing material "Tube"
         - ORDERS IDoc having PO number 12 and material "Tube".
         - MATMAS IDoc containing material "Nail"
         - ORDERS IDoc having PO number 14 and material "Nail".
c) As we see above 1st two IDocs are dependent and so are the last two.
d) Now in the receiver system the IDocs are received as follows:
         - MATMAS IDoc containing material "Nail"
         - ORDERS IDoc having PO1: 12 and material "Tube".
         - MATMAS IDoc containing material "Tube"
         - ORDERS IDoc having PO2: 14 and material "Nail".
How will serialization behave in this case. Will the system wait for all the MATMAS IDocs be posted first and then continue the posting of ORDERS IDoc (as per serialization group)? What is the internal processing logic in serialization?
If the system uses the order (as in d above) to post IDocs (which is as per the serialization order also ignoring data) then it will lead to failure of 2nd IDoc (as the material IDoc for it comes later).
Appreciate your help/inputs in this.
Thanks.
Regards,
Gajendra.

Hi,
it means that IDOCs will be received in the order in which they were send - nothing more:)
have a look at this link:
http://help.sap.com/saphelp_nw04/helpdata/en/bd/277264c3ddd44ea429af5e7d2c6e69/content.htm
BTW
you can find out more about serialization of IDOCS with XI
in my book:
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi"><b>Mastering IDoc Business Scenarios with SAP XI</b></a>
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

How to check IDOC Serialization for custom idoc

In one of my interfaces, we are receiving idocs ARTMAS, INFREC, COND_A and ZMD_ARTHIER in ECC system.Last one is customized one in which basically we have to assign one article to an article hierarchy. So this idoc will contain only article no, hierarchy id and node level in which article will be assigned.
Now here we have to implement idoc serialization so that if ARTMAS in any case fails then INFREC, COND_A and ZMD_ARTHIER idocs should not be posted. We will be using RBDSER04 program for inbound processing.
My concern is that whether we have to do any special coding for serialization check in custom function module for the last idoc ZMD_ARTHIER.
If yes, please please let me know how to do handle that in custom inbound function module.
Edited by: suman pandit on May 19, 2009 10:47 AM

Hi,
you need to create a serialization group (in customizing) and assign all the IDocs (in specific order) to this group incl. your custom IDoc.
When data is transfered first a SERDAT01 IDoc will be sent, after this your IDocs have to follow in specific order. At last again a SERDAT01 follows and triggers the processing in the destination system.
Regards,
Kai

Idoc serialization and change pointers automatic trigger

Hello Experts
How to trigger an Idoc automatically once the application has been saved ?
Scenario 1: Here serialization of message types are used, all the idocs in the serialization group must trigger & sent to the receiving system as per the sequence even if any field in the complete serialization group of message type changes (Note No Manual processing using reports Like RBDSER01, RBDSER02 etc..or Batch Jobs)
Scenario 2: Again Idoc has to trigger and sent to the receiving system as per the change pointer configuration once the application has been saved (Note: No manual processing like BD10, BD11 etc.. and no user exits has to invoke while saving the application).
Please let me know is this two cases can be implemented. Thank you in Advance.
Regards
Imran.

Hi Fernando,
I'm trying to accomplish the same thing that you were... trying to get a change pointer to be created based off the status change of a technical object (functional location or equipment).
Can you give me any detail on what you did?
Thanks,
John

Idoc serialization for vendor and address master

Hi friends,
My gole is to transfer vendor master data from one sap ecc system to other ecc through PI.
I have achived this but the gmail and address data is not transfering as this is not a part of vendor master but even this address data need to passed to receiver system when ever there is change and creation of vendor.
Then i refered note Note 752194 - Serialization of IDoc processing and few threads in sdn ..
i am trying to do this serialization but i am facing issues to trigger idocs.
first this is the way we need to achive this.
if so adrmas is of type bapi so how can we group using Serialization Group of mesage type ..
guide me how to achive this.
And my vendor message type is customized one with zcremas_Xxx.
Regards
Vijay
Edited by: vijay Kumar on Dec 16, 2010 6:48 AM

Hi Vijay,
I am not sure whether you are active in SDN or not. I need your help in IDOC serialization
I have the same requirement like you here I need to Post ADRMAS and CREMAS. I am able to generate both the idocs succefully but the ADRNR is not assigned to the created Vendor. I might be missing something in config or in code.
Please reply to this thread and help me.

Idoc serialization for custom message types

Hello,
We have a scenario where we need to serialize outbound messages where the message types are both custom and SAP standard. Can we serialize custom message types and how?

Hi,
you need to create a serialization group (in customizing) and assign all the IDocs (in specific order) to this group incl. your custom IDoc.
When data is transfered first a SERDAT01 IDoc will be sent, after this your IDocs have to follow in specific order. At last again a SERDAT01 follows and triggers the processing in the destination system.
Regards,
Kai

Idoc Serialization for Transactional data

Hi All,
1. Please let me know if you have done IDOC serialization for Transactional data.
If so please let me know the steps.
2. How do we use serialiazation using object types. If you have done this please let me know the steps for this too.
Thanks for your help.
Srikanth.

Hi Srikanth,
Follow the steps below to set up serialization using object types:
1.       In the SAP menu choose ® IDoc Interface/ALE ® Development ® BAPI ® Serialization ® Serialization Using Business Objects ® Determine Supported Business Objects (transaction BD105). Enter all the business object types relevant for serialization.
2.       In the SAP menu choose ® IDoc Interface/ALE ® Development ® BAPI ® Serialization ® Serialization Using Business Objects ® Assign Message Type to a Business Object (transaction BD104). Assign the message types relevant for serialization to each business object type.
3.       In Customizing (IMG) activate the serialized distribution in both the sending and receiving systems:
ALE Implementation Guide (transaction SALE)
Modeling and Implementing Business Processes
Master Data Distribution
Serialization for Sending and Receiving Data
Serialization Using Business Objects
Execute activities Activate Outbound Business Objects and Activate Inbound Business Objects. Set the Serialization flag for the required business object types.
If you want to do serialization by message type then
1. go to BD44 and create a serialization group and assign messages and the serial number to each.
2. Run the program RBDSER01.
Award points if useful,
Aleem.

Error while posting Customer with Multiple sales areas using DEBMAS05.

Dear experts,
We are generating IDOCS vis SAP DS for posting Customer master. The message type used is DEBMAS and basic type is DEBMAS05. we have a requirement to create 1 customer with multiple sales areas. However, we are ending up with a strange error: "Fill all required fields SAPMF02D 0111 ADDR1_DATA-NAME1". Despite the IDOC going into status 51, the customer gets created and the 1st sales area too. the 2nd sales area however is not created! The IDOC data definitely contains Name1, otherwise the customer would not have been created in the first place.
As the error message is related to the Address data, I also explored upon exploring this erorr further on the lines of Central Address management where in the ADRMAS and DEBMAS have to be passed together(IDOC Serialiization). OSS Note (384462) provides further details about this. One Important point from the note is:
"As you have to specify the logical name of the sending system among other things, SAP is not able to make any default settings in the standard systems. When you use the serialization groups delivered as a standard by SAP, the address objects are imported before the master objects.Thus the sequence address data before master objects must only be adhered to if one of the following points applies to your application:
Such fields are set as required entry fields that are only provided by the BAS in the Customizing of the customer or vendor master.
For your customers, contact persons exist to which a private address or a different business address is assigned.".
This is not the case in our situation, as we do not have required entry fields in customizing that are only provided by the BAS, so the error is all the more confusing and I am not too sure what the cause is.
If someone have experienced the same issue before and have found a solution to it, kindly help out.

I have found the cause and solution to this problem.
This error ”Fill all required fields SAPMF02D 0111 ADDR1_DATA-NAME1” and other similar errors like “Fill all required fields SAPMF02D 0111 ADDR1_DATA-SORT1“ which occurrs during the IDOC posting when there are more than one sales area or company code occurs when the customer number range is set up for Internal numbering. This means, that the number gets generated only at the time of save and upon debugging the IDOC, we found out that after creating the customer and the first sales area/company code record, the segment E1KNA1M is cleared completely! This is the reason, it throws an error which points to a mandatory KNA1 field as missing. (Like NAME1, SORT1 etc.)
This was resolved by splitting the IDOC into 2.
The solution is to First post only the KNA1 segment and create the customer.
In the second step, pass the IDOC with all other segments along with E1KNA1M, but pass only KUNNR in E1KNA1M and the rest of the fields in E1KNA1M as “/”: you would have got the KUNNR after the first step.
Important note: This requirement to split the IDOCs does not occur when the customer number is known upfront. (Meaning cases where the customer number is externally generated) I also tested this and created a customer with external numbering and I was able to post more than 1 sales area with the same IDOC.
I noticed multiple threads with the same issue, but none of it had a concrete answer. I hope this information will be useful for anyone facing similar problems.
Cheers
Venkat

Problem in ALE Idoc

Dear All,
We have transferred master data from one client to another using Ale - Idoc methodology. But it has been observed that complete master data not transferred to destination client.
Now I want to know how to find out missing information through standard method because it is not feasible to check line by line every master data.
Thanks,
Rameshwar.

Hi,
When master data is distributed, interdependent objects are often distributed together. With serialized message distribution IDocs are created, dispatched and posted in a specific order. The interdependency of objects is at message type level and this avoids errors occurring during inbound processing of IDocs. Serialization groups in which the messages to be used and the posting order is specified, are used to distribute interdependent messages serially.
For example:
If you distribute materials and the material classes, they must be distributed together. You cannot process classification data in the receiver system, if this system does not also have the data of the material to be classified
Todo this......Follow the below steps
1) Define serialization groups
2) Assign Message types to the serialization groups
The distribution model should have all the message types defined in the serialization groups, add additional message type SERDAT

Idoc multi mappings in a single interface

Hello Folks
I have to send three different types of Idocs (MATMAS, CLFMAS, BOMMAT) from R/3 to XI.
The sender application sends only one file and I need to map the data relevant to each of these Idocs and post in R/3 separately in a defined sequence. Customer wants me to incorporate all of these idocs in a single interface. How can I achieve this?
If I want to create the interfaces separately in XI for each Idocs, then how can I use the same inbound file to XI for all of the Idoc interfaces?
Which is the best way to achieve this type of scenario? I would like to know the solution without BPM preferably.
Thanks
Ricky

Hi Raj
This is the scenario again
Send a single File from a sender application.
Receive the file in BPM.
Create three message mappings/interface mappings for MATMAS, CLFMAS and BOMMAT in XI repository separately for each.
The file has the data for these three idocs. I wil keep the file message type as the same source for these three interfaces in the mapping and change the target message type accordingly.
Create a interface determination with three interface mappings involved.
Create a receiver determination
Create a receiver R/3 at the end to receive the messages.
For all these three idoc interfaces, I am going to use a single receiver agreement and sender agreement
In this BPM, the ALEAUD message should also be incorporated. When the MATMAS is send across to R/3, I need to receive the ALEAUD from R/3 and find the status of this. If it is success, then send the CLFMAS to R3 or else, roll back the MATMAS idoc sent and end the process. If CLFMAS is also success, then send the BOMMAT idoc or else, roll back the BOMMAT idoc and end the process. If BOMMAT is also success, then end the process.
In R/3, I have to run the report RBDSER04 to generate and post the idocs based on serialization group. Here I am not sure about how to use the roll back of Idocs sent to R3 in BPM since the idoc is only generated and posted together when this report is executed. SO what do we do to roll back the message sent from XI to R/3?
Thanks
Ricky

Merchandise category & hierarchy upload using LSMW???

Hi
I am trying to upload Merchandise category and hierarcy using LSMW (BAPI/IDOC method only).
For merhcandise category
I used message type W_WGRP and it is helping me in changing or reclassification of articles. But I am not able to create new merchandise category with this. I used structure E1BPE1WGR01 with "function" field with value "005, LSMW is working fine idocs are created successfully but no new Merc Cat is created.
When I used same structure with "function" field with value "009" I get error message "Class XXX does not exist or or is not valid on this date".
For Merchandise Catrgory Hierarchy
I used idoc CLSMAS but getting error message "Keyword missing for class XXX"
has anybody uploded entire hierarchy structure using LSMW ?

Sorry to say, but your problem is not resolved.
In IS-Retail, a merchandise category must first be created as a class (CLSMAS) and then also as a merchandise category (W_WGRP). Yes, you must process two IDoc per merchandise category, and in that order.
To understand how to load data using LSMW, the best approach to watch what the system does naturally. In this case, use T-Code WGSE to send the merchandise category hierarchy via ALE from one system-client to another. For understanding, you needn't configure the entire ALE scenario, just the outbound portion. Then watch the outbound IDocs be created; there's your example!
For merchandise category hierarchy (including merchandise categories), there are four message types that will be sent: W_WGRP, CHRMAS, CLFMAS, and CLSMAS.
IDoc Serialization using message types (serialization groups) is used when several different message types are dependent on each other, as is the case here. For example, if a merchandise category is assigned to a merchandise category hierarchy level, the merchandise category hierarchy level must first exist. How you use LSMW and IDocs is informed by the sequence.
To understand the IDoc sequence for creating the merchandise category hierarchy (including merchandise categories), use T-Code BD44 to view the Serialization Group GRP_W_WGRP includes the 4 desired message types in sequence:
CHRMAS04 Distr. of Characteristics with Dependencies and Long Texts
CLFMAS02 Master object classification
CLSMAS04 Classes with Long Texts, Document Links, and E1UPSLINK
W_WGRP01 Distribution of material groups
CHRMAS04 is only relevant of Characteristics are being assigned to merchandise categories. Let us leave Characteristics aside for now.
Step 1: Create Merchandise Category Hierarchy Nodes
Step 2: Merchandise Categories - Create as a Class
Step 3: Merchandise Categories - Change as a Retail MC
Step 4: Merchandise Categories - Assign Category Hierarchy Nodes each other, and assign MC class to MCH node.
For this, use these messages:
Step 1: CLSMAS04
Step 2: CLSMAS04
Step 3: W_WGRP01
Step 4: CLFMAS02
- Paul
Paul R. Gendreau, Jr.
SAP Retail

CREMAS / ADRMAS Outbound Idoc Example

Hi All,
I need to send Vendor Data to SAP PI (This will be a daily Job, not every time vendor's data is change so no change pointers involved). I created a program to select vendors based on some criteria and then called transaction BD14. Everything ok so far but the Analyst told me they want to use CREMDM instead of CREMAS because CREMDM contains address segment that might be a requirement in the future (this is understandable...).
I searched SDN and found out that BD14 does not support CREMDM. I also read that I can extend CREMAS with Address segment. Now I have a couple of questions:
- If I extend the IDOC, I won't be able to use BD14 anymore right? I mean, I'll need to complete the segments myself and then use MASTER_IDOC_DISTRIBUTE?
- I also read there are no BD* transactions for CREMDM but there is transaction MDMV. Can I use this transaction to select Logical System as I can do it in BD14?
- I also read about Idoc Serialization. I have Serialization Group (ADRMAS / CREMAS). Can I use it for my purposes?
Any help would be appreciated.
Thanks & Regards,
Ernesto.

Hello,
I just created partner profile for dev. system clients. i.e., client 010 to 020 using BD64 for CREMDM message type.
When I run MDMV t-code it automatically picked up my receiver system at per distribution model setting.
You can also try submit report RMDMIDVE (t-code MDMV) through your custom report.
Regards,
Sameer

Tcode for IDOC

Dear friends ,
can any one give me important Tcodes for IDOC & workflow
Reddy

Tcode list for ALE IDOC:
ALE / EDI/ IDOCS TRANSACTION CODES
Transaction Code     Description
WE02     List Of All Idocs Created. (Default, Additional, EDI)
WE05     List Of Idocs Created.    (Standard, Additional)
WE06     Active Monitoring For Idoc Processing.
WE07     Idoc Statistics.
WE08     Display View u201CFile Statusu201D:Overview-Path Name.
WE09     Idoc Search For Business Contents (Database).
WE10     Idoc Search For Business Contents (Archive).
WE12     Modification Of Outbound File, Triggering Inbound Processing.
WE14     Process All Selected Idocs.
WE15     Selection Program For Issuing Output.
WE16     Trigger Inbound Processing.
WE17     Trigger Status Processing.
WE18     Generate Test Status File For Outbound Idocs.
WE19     Test Tool For Idoc Processing
WE20     Partner Profile.
WE21     Ports In Idoc Processing.
WE23     Display Test Catalog Test Idoc Interface.
WE24     Maintain Table View. Direction-1.(Outbound)
WE27     Maintain Table View. Direction-2.(Inbound)
WE30     Develop Idoc Type.
WE31     Develop Idoc Segments.
WE32     View Development.
WE33     Maintain Table Views.
WE34     Change View u201CTable Of Style Ids With The Objects To Be Loadedu201D
WE40     Display System Process Code.
WE41     Display View: Logical Msg Overview. For Outbund.
WE42     Display View: Logical Msg Overview. For Inbound.
WE43     Display Status Records.
WE44     Display Partner Types
WE45     Maintenance Interface: Forwarding Inbound/EDILOGADR For Application
WE46     Global Parameter For Idoc Interface.
WE47     Status Maintenance.
WE50     Display Text For Process Code System.
WE54     Idoc Function Module For File Name
WE56     Display Status Process Code
WE57     Idoc Assignment Of FM To Log. Message And Idoc Type.
WE58     Text For Process Code Status.
WE60     Documentation For Idoc Type.
WE61     Documentation For Idoc Record Type.
WE62     Documentation For Idoc Segment Type.
WE63     Documentation For Idoc Record Types And Idoc Types (Parser).
WE64     Process Code In Idoc Inbound And Outbound.
WE70     Conversion Table For Basic Types.
WE71     Conversion Table For Extensions.
WE72     Conversion Table For Field DOCTYP.
WE73     Conversion Table For Logical Message Type.
WE81          EDI:Logical Message Type.
WE82     Message Types And Assignment To Idoc Types.
WE84     Assignment Table Between Idoc And Application Field.
ALE / EDI/ IDOCS TRANSACTION CODES
Transaction Code     Description
BD10     Send Material (Matmas)
BD11     Get Material.
BD12     Send Customer.
BD13     Get Customers
BD14     Send Vendor.
BD15     Get Vendor.
BD16     Send Cost Center. (Cosmas)
BD17     Request Cost Center.
BD18     Send G/L Accounts.
BD19     Get Master Data G/L Accounts.
BD20     Inbound Processing Of Idocs Ready For Transfer.
BD21     Creating Idoc Types For Change Pointers.
BD22     Delete Change Pointers.
BD23     Serialization Using Time Stamp: Deletion Of Old Time Stamp.
BD24     Send Cost Elements.
BD25     Send Activity Type (COAMAS)
BD26     Request Activity Type
BD27     Cost Center/Activity Types: Transmit Plan Quantities And Acty Prices.
BD28     Cost Center/ Cost Elements: Send Control Records.
BD30     Material Bom Distribution. (Bommat).
BD31     Document Structure Distribution. (Bomdoc)
BD32     Plant Allocation To Material Boms Distribution.
BD33     Distribution Of Material Variants. (STTMAT)
BD34     Distribution Of Boms (BOMORD)
BD35     ALE: Send Business Process Group.
BD36     ALE: Send Business Process.
BD37     ALE: Send Business Process Price.
BD40     Generate Idocs For Serialization Group From Change Pointers.
BD41     Dispatch Of Idocs Of Serialization Group.
BD42     Check Dispatch Status Of Idocs Of Serialization Group.
BD43     Processing Inbound Idocs Of Serialization Group.
BD44     Change View u201CSerialization Groupu201D.
BD47     Dependence Between Methods.
BD48     Dependence Between Methods And Message Type.
BD50     Activate Change Pointers For Message Type.
BD51     Characteristics Of Inbound Function Module.
BD52     Determine Work Area.
BD53     Reduce Message Type.
BD54     Change View: Logical Systems
BD55     Idoc Conversion.
BD56     Maintain Idoc Segment Filters.
BD57     Link Type And Serialization Type Of Message Type.
BD58     Convert Organizational Unit.
BD59     Allocation Of Object Type.
BD60     Additional Data For Message Type.
BD61     Activate Change Pointers Generally.
BD62     Display Conversion Rule.
BD63     Transport Of Ale Tables For A Message Type.
BD64     Display Distribution Model.
BD65     Maintain Idoc Type Required Fields.
BD66     Change Idoc Fields.
BD67     Function Module For ALE/EDI Overview.
BD68     Maintain List.
BD69     Assignment Of Idoc Type To Message Type.
BD70     Cross-System Comparison Of Number Range Objects.
BD71     Attributes For Receiver Determination.
BD72     Active Events For ALE/EDI
BD73     Start Error Handling For Non-Posted Idocs.
BD75     Status Conversion With Trfc Execution.
BD77     Generate Transport Requests For Distributing ALE Customizing Data.
BD78     Monitoring Ale Customizing Data Transport
BD79     ALE IDOC Segments - Conversion Rule
BD81     Filter Objects For BAPI Parameter Filtering
BD82     Generating Partner Profile
BD83     Re-Processing Incorrect Outbound Odocs.
BD84     Re-Processing Of Idocs After ALE Input Error.
BD85     Consistency Check: Reassignment Between Two System.
BD86     ALE Consistency Check: Create Purchase Order From Sales Order.
BD87     Select Idocs
BD89     Customizing Data Modeling For Distribution Model.
BD91     Distribute All Characteristics Via ALE.
BD92     Distribute Class Via ALE: Send Direct.
BD93     Distribution Of Classification Data Via ALE.
BD95     Ale Object View
BD96     Filter Object For Receiver Determination Of Methods.
BD97     Assign RFC Destination For Synchronous Method Calls.
BD98     Consistency Check With Workflow Link
BD99     Dependencies Between Message Types.
BD100     Display Serialized Idocs. (Serialization Using Object Types)
BD101     Serialization Using Object Types: Consistency Check.
BD102     Ale: Outbound Channel Registry.

Serialization group

Similar Messages

Maybe you are looking for