IDoc Serializing

Hi,
I have been through all the blogs, I am looking for a IDOC serialization step by step guide for posting idocs to ECC from PI.
All the blogs deal with outbound from ECC..
PB

Incase if you are looking for XI to ECC Serialization . You can Use SETDAT IDOC Configuration to solve the problem .
-Create a serialization group(txn BD44) and assign the message types and the sequence in which the mesage types needs to be generated.
-Whenever serialization comes into picture, SERDAT message type needs to be configured. Update the distribution model and partner profile with the serialization message types(MATMAS, CLFMAS, SERDAT) and distribute the model view.
- At the inbound side, Goto transaction SALE and traverse through Modelling and implementing busines processes -> Master Data Distribution -> Serialization for sending and receiving data -> Serialization using message types -> Define inbound processing, wherein add the serialization group and the message types under the group. The RFC server group which needs to be filled in here could be obtained from transaction RZ12.
For SERDAT Mapping . You just need to Populate the SeqNumber , SerGroup and Message Type .
In Partner Profile Set the MATMAS CLFMAS as process in Background , SERDAT as Process Immediately.

Similar Messages

Help required in posting inbound idocs

Hi,
We are facing a problem during integration testing to post inbound idocs.
The scenario is :
A custom FM is written to process the inbound idocs, which does the following processes in sequence.
1. BAPI used to create Goods Receipt
2. BDC used to create Delivery using VL01N
3. BDC used to create Handling Unit using VL02N
4. BDC used to create Post Goods Issue using VL02N
The VL01N creates a deivery, and using that delivery BDC calls VL02N to create HU.
In unit testing the idocs are success, but when multiple idocs are used in integration testing, all fails either during delivery creation or HU creation.
The error message we often get when HU is failed is : "Runtime error RAISE_EXCEPTION has occured ".
We have also incorporated a commit work and wait of 5 seconds after each BDC to avoid locking problem if any.
The partner profile is set to ' trigger by background program'.
Standard program RBDAPP01 is scheduled to collect the IDocs in status 64 and then to be processed.
The package size used is 1, inorder to process idocs one by one to avoid locking.
Should any object type be given in RBDAPP01 ?
If so, is it required to maintain any record for that object type in table TBD55 to process idocs serially in RBDAPP01 ?
Any help in this regard is appreciated.
Thanks in advance
Regards
Meena George

Hi,
We are facing a problem during integration testing to post inbound idocs.
The scenario is :
A custom FM is written to process the inbound idocs, which does the following processes in sequence.
1. BAPI used to create Goods Receipt
2. BDC used to create Delivery using VL01N
3. BDC used to create Handling Unit using VL02N
4. BDC used to create Post Goods Issue using VL02N
The VL01N creates a deivery, and using that delivery BDC calls VL02N to create HU.
In unit testing the idocs are success, but when multiple idocs are used in integration testing, all fails either during delivery creation or HU creation.
The error message we often get when HU is failed is : "Runtime error RAISE_EXCEPTION has occured ".
We have also incorporated a commit work and wait of 5 seconds after each BDC to avoid locking problem if any.
The partner profile is set to ' trigger by background program'.
Standard program RBDAPP01 is scheduled to collect the IDocs in status 64 and then to be processed.
The package size used is 1, inorder to process idocs one by one to avoid locking.
Should any object type be given in RBDAPP01 ?
If so, is it required to maintain any record for that object type in table TBD55 to process idocs serially in RBDAPP01 ?
Any help in this regard is appreciated.
Thanks in advance
Regards
Meena George

IDOC Serialization Processing

Experts,
Request your view on this:
The scenario is File to IDOC via XI. XI picks up the XML files via a file adapter which is then mapped to idoc ZRMD_A07 (HRMaster Idoc Basic type built as a copy of HRMD_A07 to add additional infotypes) and sent to SAP ECC via IDOC Adapter.
This interface is live and works well for the partner profile setting in WE20 as Trigger immediately.
The most important requirement of the scnario is to process the idocs serially as the following IDOCs may depend on the previous one.
The trigger immediately caused resource issues when there were 45000 idocs hit the system. So we decided to process them in background by chaging the partner profile setting as Triger by background Job. We scheduled the report RBDAPP01 for the same.
It caused problems as the idocs were not processed serially. So we did the settings in SAP ECC system to have the IDOCs posted in the status 66 which tells the background program to process them serially.
I followed the following links on help to post idocs with status 66 but still they are getting posted as 64:
http://help.sap.com/saphelp_nwpi71/helpdata/EN/f8/42d1b5cfa711d6b2ba00508b5d5c51/content.htm
http://help.sap.com/saphelp_nwpi71/helpdata/EN/5f/45f93b4139b478e10000000a11402f/content.htm
Any help would be much appreciated.
Regards,
Ripple

How about placing the IDOCs in a queue. If you setup the file adatper as EOIO and provide a queue name, then in your ECC system, the IDOCs will be posted using the same queue name and can be displayed using transaction code WEINBQUEUE.
You can use program RSEINBQUEUE_PARTNER to post these IDOCs within the queue.
Queuing up/serializing impacts performance as well because you are not posting IDOCs in parallel. Another round about Idea is to post the IDOCs through a proxy in multiple queues where you can group IDOCs that need to be serialized in a particular queue. I wouldn't know a reason why all the 4500 so IDOCs need to serialized. Normally it is a set of IDOCs within the 4500 that need to serialized.
KK

Order of Idocs

In a current integration project with SAP, we found that SAP processes inbound IDocs not necessarily in the order which they were received and meant to be posted; leading to undesired order of postings and inconsistent data replication across various systems.
As a result, another SAP developer and I designed a solution where my source system delivered the IDoc to the destination SAP system and we referenced a parent IDoc serial number in the IDoc header. The IDoc processing engine examined this field and validated whether the IDoc referred by that serial number was successfully posted or not. If not, the subsequent IDoc was left queued for processing; however, if the parent was posted successfully, it continued to post the subsequent IDoc. This insured that the postings inside the destination SAP system were in the desired order the business required.
As we take a step in the future and look at streamlining our approach, strengthening our code base, and to continue to maintain business requirements between both the source system and SAP; I hope the developers here can help with my questions.
Is there a way to insure ordered processing of inbound IDocs to SAP without any special or heavy customizations?
For example, if I post a 101 (po receipt) followed by a 201 (goods issue) to a remote SAP system and both Idocs are movements for the same item and storage location, I would want the 101 to be processed first and immediately followed by the 201. Likewise if the movement order was a 102, 101, then 201; I'd like to force the Idoc processing engine to process the three movements specifically in this order without any type of "retry"/"reprocess" construct.
Is this possible?
From the SAP side, to give a baseline of which version/platform; I'm speaking specifically toward SAP release v4.6c and v4.7.
Thanks!

Moved to IDOC area; posted in wrong forum.

Error in idoc posting

We have a scenario where some 20 to 25 Idocs which r at 64 status are processed by the batch program(for rbdapp01) to post them in the system.What happens is some idocs take few extra secs for processing so the the other idocs get posted in 51 status saying material and batch is locked by the batch program....
what we do is we go reprocess the idocs manually..
This happens frequently now...
So whatz the possible solution for this...?
Pls help...
Thanks,
Larry

Here is the documentation of the program RBDAPP01 which I am sure you might have read. Packet size has a role to play in it, but locking issues are typically due to parallel processing. Also, it could be the time of the day. Say you run this when there is lot of activity, online or background that also has something to do with the material/plant/batch etc. In that case, even if you have your IDocs serialized, you will still be facing the same issue as now the locks are created by other processes.
<i>
Short text
Inbound Processing of IDocs Ready for Transfer
Description
Report for processing inbound IDocs not passed to the application immediately.
This report forwards all IDocs with:
Status 64 "ready to be passed to application"
Status 66 "IDoc is waiting for predecessor IDoc (serialization)
These match the selection criteria to be passed to the application for further processing.
Essentially there are two groups of IDocs:
IDocs to be serialized in accordance with the associated object.
All other IDocs
There are also two types of processing:
Serial processing (IDocs are processed one after each other in one process)
Parallel processing (IDocs are passed in packets to other processes for processing).
Purpose of parameter 'Packet size': For IDocs to be serialized by object and for activated parallel processing, this parameter specifies the size of a packet to be processed in a task. If applicable, independent objects are processed in a separate task as with serial processing. (Large packet sizes lowers the level of parallel processing).
For all other IDocs, as far as possible, an appropriately sized document is passed to the application. On the one hand, this supports some applications capable of mass processing. On the other hand, the number of parallel packets is less as with activated parallel processing. (Lower system load, longer runtime).
Notes on Program Terminations in Parallel Processing
In parallel processing, processes containing the IDocs to be processed are started in parallel. If there is a termination (dump/ A message), no message is issued by RBDAPP01. The best way to identify such problems is to run RBDAPP01 without parellel mode after a scheduled RBDAPP01 with parallel mode. Then a termination is logged (dialog message or message in job log).
Output
The processed IDocs are output.</i>

Help in inbound idoc posting using bdc

Hi,
We are facing a problem during integration testing to post inbound idocs.
The scenario is :
A custom FM is written to process the inbound idocs, which does the following processes in sequence.
1. BAPI used to create Goods Receipt
2. BDC used to create Delivery using VL01N
3. BDC used to create Handling Unit using VL02N
4. BDC used to create Post Goods Issue using VL02N
The VL01N creates a deivery, and using that delivery BDC calls VL02N to create HU.
In unit testing the idocs are success, but when multiple idocs are used in integration testing, all fails either during delivery creation or HU creation.
The error message we often get when HU is failed is : "Runtime error RAISE_EXCEPTION has occured ".
We have also incorporated a commit work and wait of 5 seconds after each BDC to avoid locking problem if any.
The partner profile is set to ' trigger by background program'.
Standard program RBDAPP01 is scheduled to collect the IDocs in status 64 and then to be processed.
The package size used is 1, inorder to process idocs one by one to avoid locking.
Should any object type be given in RBDAPP01 ?
If so, is it required to maintain any record for that object type in table TBD55 to process idocs serially in RBDAPP01 ?
Any help in this regard is appreciated.
Thanks in advance
Regards
Meena George

Refer these links and see if they are useful:
http://help.sap.com/saphelp_nw04/helpdata/en/0b/2a66c9507d11d18ee90000e8366fc2/content.htm
Regards,
Ravi

How to Serialize IDOCs

Hi,
I have a program who is creating DEBMAS IDOCs. The case is that the program creates four IDOCs for each customer (for each CC).
The IDOC is posted using IDOC_INBOUND_SINGLE.
The problem is that the DEBMAS IDOC of course blocks the customer number. So i was wondering if Serialization was a possibility?
But how do i post the IDOCs "Serialized" ?

Hi,
I have a program who is creating DEBMAS IDOCs. The case is that the program creates four IDOCs for each customer (for each CC).
The IDOC is posted using IDOC_INBOUND_SINGLE.
The problem is that the DEBMAS IDOC of course blocks the customer number. So i was wondering if Serialization was a possibility?
But how do i post the IDOCs "Serialized" ?

IDOC message type WMMBXY not including Serial numbers in GR material documents when created with reference to an Inbound delivery

Hello,
We currently have an inbound ALE process (message type WMMBXY and basic type WMMBID02) to post GR's against inbound delivery. If the inbound delivery item is maintained with serial numbers, we want those serial numbers to be pulled into the goods movement material document (and stored in SER03).
Currently segment E1MBXYJ is maintained with the inbound delivery number in field VLIEF_AVIS and Inbound delivery item number in field
VBELP_AVIS. In segment E1MBXYI, no purchase order is assigned and the fields EBELN and EBELP are blank. The movement indicator (KZBEW) has the value 'B'.
Even after making the above settings, the serial number(s) maintained on the Inbound delivery item do not get saved to the material document.I did look at OSS note 833603 (Solution for 2 - GR for Inbound delivery) and we have followed the same settings. This works when there is no serial number in the Inbound delivery. However if we have serial numbers, the IDOC posts successfully, however the material documents in MB03 do not have any serial numbers copied over from the Inbound delivery where the serial numbers are definitely assigned.
Any help you can provide is greatly appreciated!
Thanks,
Ashvin
P.S
If we manually create the GR via MIGO, the serial numbers are automatically applied to the GR material document. This is what we want to accomplish via the above IDoc process.

Hi
Try with enhancement MWMIDO08. See note 833603 - EDI: Goods receipt for stock transport order for further information.
I hope this helps you
Regards
Eduardo

Idoc DELVRY03/DESADV for Inbound delivery with serial number

Hi,
We have set up am EDI process between our vendors ERP system and our SAP. We will send purchase order Idocs to our vendor, once our vendor has shipped the goods (to our customer) he send an DESADV/DELVRY03 Idoc back to our system. This Idoc will create a statistical inbound delivery and a statistical goods receipt will be automatically created in our SAP system.
This process runs fine as long as we use materials without serial numbers. Unfortunately we have some materials which need to have a serial number assigned by our vendor and we want to keep track of this information in our SAP system.
The only place where I found a serial number field in the Idoc is in the 'E1EDL46 : Serial Numbers HU' segment in the DELVRY03 Idoc, but unfortunately we don't have handling units activated in our SAP system. So if we fill this information the Idoc processing fails.
Is there any other way to create an inbound delivery containing serial number information without activating handling units?
Thanks for your help,
Frank

Hi,
is there anyone who has experience with EDI inbound delivery postings containing serial number information?
Thank you,
Frank

Inbound idoc error in 51 Status of at least one serial number of item

Dear Experts,
There is one inbound IDOC which is in error with status 51 showing error Status of at least one serial number of item is not allowed.
Can you please advice why this error is coming.
Thanks & Regards,
Nikhil Kanegaonkar.

An inbound IDOC in error will have the status 51, & it is marked for deletion it has a status of 68.
http://www.dataxstream.com/2009/10/mass-status-change-sap-idoc/
http://wiki.sdn.sap.com/wiki/display/ABAP/IDoc+Statuses
Edited by: Krupaji on May 6, 2011 2:38 PM

Serializing IDocs

Hi,
My scenario is IDoc to File. I want to serialize IDocs.
Where will I specify quality of service EOIO.
Thanks in advance,
Neena

Hey,
I am sry for that..
The quality of service EOIO (Exactly Once In Order) must be specified in the message header
Prerequisites
· The quality of service EOIO (Exactly Once In Order) must be specified in the message header.
· The receiver system or the sender system must be based on SAP Web Application Server 6.40 or higher. If this is not the case, the quality of service is automatically changed to EO for compatibility reasons and the message is processed accordingly.
Procedure
If you want the Integration Server to process the IDoc XML messages created by the IDoc adapter in the same sequence that the IDocs are sent by your application, proceed as follows:
· Enter a queue name in your application. You can use 16 alphanumeric characters. The prefix SAP_ALE_ is then added.
The IDoc adapter checks the prefix and replaces it with the prefix of the corresponding Integration Server inbound queue (for example, XBQI0000).
If you want the receiver to receive the IDocs in the same sequence that they are sent by the Integration Server using the IDoc adapter, proceed as follows:
· In the communication channel, select the check box Queue processing for the receiver.
The IDoc adapter replaces the prefix of the outbound queue (XBQO) with the prefix SAP_ALE_.
You can display the individual messages in the qRFC monitor of the outbound queue. To do this, do one of the following:
¡ Use the queue ID in the list of displayed messages in the monitor for processed XML messages.
¡ Use the transaction ID in the list of displayed XML messages in the IDoc adapter.
¡ Call the transaction qRFC Monitor (Outbound Queue)(SMQ1).
To navigate directly to the display of messages in the IDoc adapter, double click the transaction ID of a message in the outbound queue.
To do this, you must have registered the display program IDX_SHOW_MESSAGE for the outbound queue in the qRFC administration (transaction SMQE) beforehand.
In both cases, the function module IDOC_INBOUND_IN_QUEUE is called, which enables EOIO processing of the messages. The processing sequence is determined by the sequence of the function module calls.
Unlike the other function modules (interface versions from the communication channel), with this function module you have to transfer segment types rather than segment names in the data records.
Serialization of Messages
Use
Serialization plays an important role in distributing interdependent objects, especially when master data is being distributed.
IDocs can be created, sent and posted in a specified order by distributing message types serially.
Errors can then be avoided when processing inbound IDocs.
Interdependent messages can be serially distributed in the following ways:
Serialization by Object Type
Serialization by Message Type
Serialization at IDoc Level
(not for IDocs from generated BAPI-ALE interfaces)
Serialization at IDoc Level
Use
Delays in transferring IDocs may result in an IDoc containing data belonging to a specific object arriving at its destination before an "older" IDoc that contains different data belonging to the same object. Applications can use the ALE Serialization API to specify the order IDocs of the same message type are processed in and to prevent old IDocs from being posted if processing is repeated.
SAP recommends that you regularly schedule program RBDSRCLR to clean up table BDSER (old time stamp).
Prerequisites
IDocs generated by BAPI interfaces cannot be serialized at IDoc level because the function module for inbound processing does not use the ALE Serialization API.
Features
ALE provides two function modules to serialize IDocs which the posting function module has to invoke:
· IDOC_SERIALIZATION_CHECK
checks the time stamps in the serialization field of the IDoc header.
· IDOC_SERIAL_POST
updates the serialization table.
Check the following link:
http://help.sap.com/saphelp_nw04s/helpdata/en/0b/2a66d6507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/78/2175a751ce11d189570000e829fbbd/frameset.htm
/people/community.user/blog/2006/11/04/how-to-serialize-idoc-xml-messages-fed-into-xi
Thanks,
Vijaya

Picking not done for a serialized material using Idoc type SHPCON/DELVRY03

Hi All,
I am using Idoc of type SHPCON/DELVRY03 to do the picking for an outbound delivery.
The value 'PIC' is populated in the qualifier of segment E1EDL18 . In order to update the batch number of the material in a delivery the qualifier of segment E1EDL19 is populated with value 'BAS' .
To update the serial numbers for a serialized material in an outbound deliverfy , BDC for transaction vl02n is used. Also the segment E1EDL24 is populated with material no. POSNR and other details , then segment E1EDL11 is having the value of serial no. Similarly for other serial number there is one more segement E1EDL24 with same material no. but E1EDL11 with other serial number.
The issue is that after the Idoc is successfully processed , picking quantity is updated only for one serial number for a serialized material of the outbound delivery. The picking quantity for other serial number is not updated . Initially the delivered quantity for the serialized material was 2 but after processing the Idoc the picking qunatity updated is 1 ( for one serial number only ).
Please provide any pointers on this.
Thanks & Regards,
Tanushri.

The firs thing I would do is verify the config. Make sure the message type of the created IDocs matches the message type to which the filter is applied in the distribution model. If everything looks ok, place break-points at the following locations:
In FM MASTER_IDOC_DISTRIBUTE, on the call PERFORM DIST_MODEL_READ_FOR_MESTYP. This subroutine reads the filters from the distribution model. Verify the values in internal table RECEIVERS_AND_FILTERS are correct.
In FM MASTER_IDOC_DISTRIBUTE, in FORM IDOC_SELECTION_AND_SERVICES, on the call to FM IDOC_DATA_APPLY_FILTER_VALUES. This function should return the filtered results. IDOC_DATA contains the data segments of your IDoc and CONDITION_BLOCKS contains the filter.
When you run BD21, you should hit these break-points.

Urgent!!! - Serial numbers in ORDERS (ORDERS05) idocs

Hi,
I have to extend the idoc ORDER05 with one additional segment in order to use it for serial numbers in the inbound IDOCs comming from a non-SAP system.
Can anyone give me an idea how to process these serial numbers in the sales order?

Hello Ivan,
I have a same requirement like yours.
Did you solve this serial number population?
what all steps you plerformed.
I m a beginer in SAP ABAP so thanks to help me in this regard.
This s quite urgent so please reply me back at the earliest.....
Thanks,
Devasing.

Serial numbers in ORDERS (ORDERS05) idocs

Hi,
I have extended the idoc ORDER05 with one additional segment in order to use it for serial numbers in the inbound IDOCs comming from a non-SAP system.
Can anyone give me an idea how to process these serial numbers in the sales order?

is this serial number is onlly for reference
then put this field in reference field of sale order...or reference document number..
otherwise u shud code in user exit to put the field value of idoc in proper scsreen field..
i ll try to give some user exits for this..can u please tell me in which field of screen u want to display this serial number
regards

Populating serial number in the Inbound IDOC WMMBID01

I have the requirement in my project to populate Serial number via incoming idoc WMMBID01. I have created an extended idoc with a Z segment added to IDOC WMMBID01. Could anybody please let me know what would be the posting logic for this serial number.
Thanks,
Chenni.

Hi,
Maintain partner profile (Transaction code WE20) for the message type you defined in WE81 and put your process code in partner profile and check your logical system settings also in transaction SALE.
Thanks
Rahul

IDoc Serializing

Similar Messages

Maybe you are looking for