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

Similar Messages

Idoc serialization by Time Stamp

Hi,
I have a need to use Idoc serialization by Date and Time, but from what I noticed the existing program 'RBDAPP01' will automatically turn on serialization by date and time stamp once the field EDIDC-SERIALIZATION is used.My understanding on serialization by Date and Time is as follows:
Once the Serialization object is defined for a unique key (By defining Serialization in 'BD95' and 'BD57'), the function 'IDOC_SERIALIZATION_CHECK' is called in inbound function module for the idoc to see if there is already a record processed for the same key (via table BDSER), and if it is then any Idoc with a time stamp less than the one in BDSER comes for processing it gets an error.
Now my questions is what is the purpose of defining the configuration for Serialization by going to 'BD95' and 'BD57' when RBDAPP01 is already doing the same?
Also please correct me if I there is any flaw in my understanding.
Thanks in advance.

Hi,
Based on what I understood from some SAP documentations (I am not 100% sure though), RBDAPP01 talks about IDoc serialization & the other transactions talks about ALE Serialization. Both are different as I understood from SAP documentation. And ALE serialization is used when you try to send a set of data. LIke material master, classification data. And you can link/serialize these different message types to make sure first material master idoc is processed & after that classificaiton idoc. And IDoc serialization is used to make sure the idocs (same message type) are processed in the same order by using field EDIDC-SERIAL. Something like date/time stamp can be used for this.
Regards,
Gokul

IDoc Inbound Processing for CREMDM & DEBMDM

Hi experts,
I'd like to gather some feedback from you regarding the topic ERP IDoc Inbound Processing for CREMDM & DEBMDM. As you all know, there's currently no option to directly process CREMDM/DEBMDM IDocs in ERP. Currently you have to use PI for splitting the CREMDM/DEBMDM message into its related ADRMAS and CREMAS/DEBMAS IDocs.
My areas of interest are:
1) How satisfied are you with the current situation? Does the split work? Are there issues or problems in the current message handling? What are the Pro's and Con's from your point of view?
2) What would be the requirements for a CREMDM/DEBMDM handler? What would you expect? Maybe you have implemented something similar on project basis and could post some feedback?
One painpoint I'd see with a CREMDM/DEBMDM inbound is that you'll lose the IDoc Monitoring capabilities. The message split allows a single record tracing in the IDoc Monitor (as there is a 1:1 relation between IDocs and records). This changes for the mass processing. The monitor would display only the status of the IDoc and you'd need some other monitoring capabilities to check the results on record level. What are your thoughts about that? Is the monitoring important? Would the application log be a feasible solution for that challenge?
Additional comments are welcome, of course.
Best regards
Michael
PS: @ Matt, please contact me by mail. thanks.

Hello ,
Here are some other pain areas regarding the message split :
1. Complicated monitoring proess & reprocessing error idocs : We have to monitor ADRMAS & CREMAS or ADRMAS & DEBMAS during inbound processing. Also we could not find any best practices to reprocess error idocs. E.g. If ADRMAS fails & CREMAS succeeds what is the impact . Also the impact if it is reveresed. We know for sure that if CREMAS fails , vendor will not be created / updated. But we could not find specific pointers for ADRMAS failures.
2. It is a tedious process to link CREMAS with corresponding ADRMAS idoc specially when SAP maintains internal number range for vendors.
3 . The process is complicated if you are managing customer or vendor contact information with contact address . We could succesfully implement the integration but it took us a while to reach end-point.
4. Splitting really does not seem to support if ERP maintains internal number range.
5. Another major issue we observed is , if ADRMAS is under process & corresponding DEBMAS or CREMAS is posted , it fails raising the message that Account is locked. Default serialization does work in ERP system . But overlap of few microseconds also cause this error.
Hope this helps !!
Please let me know if you need any other specific details since we have used MDM - ECC integration using PI to its maximum extent .
Regards
Yogesh

HRMD_A IDoc Serialization Help

Hi,
I have a client that wants to activate IDoc serialization for HRMD_A. They have a global system that sends HR master data to multiple regional systems, MDM and SRM.
The requirement is to serialize the IDocs for all regional systems, but not for MDM or SRM.
My understanding is that we would need to activate both outbound and inbound serialization through SALE->Modelling and Implementing Business Processes->Configure Predefined ALE Business Processes->Human Resources->Master Data Distribution->Serialize HR Master Data.
We would activate outbound in the global sending system, and inbound in each regional target system, but not in MDM or SRM.
By activating serialization, will it activate for HRMD_A only, or for HRMDA_ABA as well?
We would then need to make sure that the serialization counters are all initialized in both source and target systems. We can do this with transactions RE_RHALE_HRMDRGOUT and RE_RHALE_HRMDRGIN.
Please correct me if any of the above is incorrect?
Once serialization is activated, how will this effect the system? If for example an IDoc is sent with 100 objects, and one fails, then what status will the IDoc go into? Will all other objects process correctly? How would the error object affect subsequent IDocs?
What steps need to be taken in order to resolve the following potential IDoc errors:
- Change for person xxxxxxxx extends too far into past
Delete IDoc? What to do with counters?
- Object 01 ,z ,xxxxxxxx does not exist: infotype 1001 cannot be created.
Resend missing objects with PFAL and then reprocess IDoc?
- Relationship starting from 01 y xxxxxxxx impossible u2013 01 w zzzzzzzz does not exist/is not active.
Resend missing objects with PFAL and then reprocess IDoc?
- Personnel number xxxxxxxx is locked
Will this sort itself out, or do we need to manually reprocess the Idoc?
- Payroll area yy is locked for master data maintenance.
Reprocess the IDoc after payroll areas is unlocked?
Thanks very much for your help
Edited by: David Bann on Sep 22, 2011 4:52 PM

Hi,
If change pointers are to be written for custom fields then the change document flag at the domain level should be checked for that field. Then maintain an entry for this field in transaction BD52. Object name will be the same as the original fields. Changes to custom fields will be only picked if the change document for such fields is maintained in table BDCP.
Try now!
Reddy

IDOC Serialization issue.

Hi,
I tried to do IDOC serialization using this blog
/people/community.user/blog/2006/11/04/how-to-serialize-idoc-xml-messages-fed-into-xi
But in this blog its says to create a queue processing rule using WE85 transaction.
My system is not as WAS 6.40, so when i tried to run WE85 transaction, it says transaction doesn't exist. SAP system is of enterprise version 4.7 (WAS 6.2) and it doesn't have WE85.
What is an alternative to this and how to achieve IDOC serialization.
Thanks,
Swapna

Hi,
http://help.sap.com/saphelp_nw04/helpdata/en/bd/277264c3ddd44ea429af5e7d2c6e69/content.htm
The link above which has detail help on serialization.hope this helps.Pls check whether this helps.
Regards,
Sharath

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

How to enable IDOC serialization at message type level

Hi,
I am trying to enable IDOC serialization at message type and i am unable to achieve the desired results.
SETTINGS DONE:
I have done the settings required under SALE trsanaction
ALE IMG (transaction SALE)
   Model and Implement Business Processes
      Configure Master Data Distribution
          Set-Up Data for Sending and Receiving Serialization
              Serialization by Message Type
I have done the settings in both the receiving system and the sending system.
PROBLEM:
I am trying to send the Material classification first and then followed by Material class and then try to send the material itself to the other system. Since the serialization is enabled in the system, i was expecting that there should not be any errors.
But since the material classification IDOC is posted first it throws an error saying the Material Class does not exists. Since the serialization is enabled in the system i was expecting that the system would ensure that it post the Matrial class first and then post the material classification. I mean it would post in the order in which i have defined in the serialization.
Settings at Partner Profile.
    - I have set the trigger in background for all the message types except the SERDAT message type which is set trigger immediately.
Any idea what i am missing? Any suggestions on what needs to be done to ensure that the idoc is posted in serialization?
Edited by: Workflow learner on Jun 4, 2008 1:21 PM

Hi,
Create a custom transaction for PO Print & make the necessary changes as per your requirement In the custom program which you attach to the custom transaction you can put a validation to display the price based on user ID or some other parameters.
Thanks & Regards,

IDOC Serialization in PI

I have the scenario from ECC to ECC where communication will be between Idocs to idocs.
The Idocs involved in this process are ADRMAS,ADR2MAS,ADR3MAS,CREMAS,SERDAT from source to target system.
I have the requirement like need to send the idocs in the Prioritization order like below from PI to target system.
ADRMAS
ADR3MAS
ADR2MAS
CREMAS
SERDAT
Can i do the Prioritization before coming idocs to integration engine? if not how to set the serialization order in PI ?
Quick response would be appreciated?

You can do the IDoc serialization at the sender side
two things
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
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:
Check the link might be of help to you
at SAP TECHNICAL SITE :/Tutorials/ALE/Serialization/page1
When IDoc Serialization is required ?
http://help.sap.com/saphelp_nw04/helpdata/en/bd/277264c3ddd44ea429af5e7d2c6e69/content.htm
Regards
Ninad
Edited by: Ninad Sane on Jan 3, 2011 1:36 PM

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

IDOC serialization

Hi Experts,
I am doing the scenario file->PI->ECC.
I would like to know how can we do the IDOC serialization (Object channel serialization) .
In my case we need to ensures that documents are processed in the receiving system in exactly the same sequence in which they were created in the sending system.
As per the note 752194 the Object channel serialization will best suite my requirement.But how can i achieve when i am sending the IDOC xml from PI--> ECC.
I want to know what are the settings we need to do in XI and ECC??
Do we need to generate channel number in XI..?? if so how??
If i want to do for orders IDOC...what we need to do BD105 and BD104 transactions.??
Where we need to call ALE_SERIAL_KEY2CHANNEL function module..??
Note: I dont want the serialization for ECC--> XI

Please post this in PI forums
Anil

Error : Pre Settings for IDoc inbound processing are missing error

Hi Experts,
There is a CRM job which executes LSMW and I am facing a strange problem during the IDOC posting the error "Pre Settings for IDoc inbound processing are missing error". Can anyone please tell me how to correct this error?
Thanks in advance.
Madhurima.

I'd start with the following document, with one modification. At step 12 after typing GEARAspiWDM press the Enter/Return key once prior to clicking OK. (Pressing Return adds a carriage return in the field and is important.)
[iTunes for Windows: "Registry settings" warning when opening iTunes|http://support.apple.com/kb/TS3299]

Delay in the Inbound Idoc Posting Process

Dear Friends,
We have an scenario in the Inbound Idoc Posting Process, when we process the Idocs through the standard Inbound Program - RBDAPP01, we face the delay of 3hrs to 12 hrs, approx.
When we try to re-process the same through the manual process, we could successfully post the Idocs, immediately.
When the same happens, through the background job - the delay is happening.
As we see, there is no problem with the program - RBDAPP01, but can't able to trace the delay in the process.
Any suggestions / advises are welcome.
Thanks in advance.

Hi Prasanna,
The update will happen only if a value already exists with the same unit of measure in the system. If the quantity is left blank in the system and if you are trying to update, the update might not happen. Even if the value is Zero in the system, provide the same unit of measure as the data used in the BAPI.
Regards,
Yogesh

How to implement IDOC Serialization(EOIO) using IDOC Adapter

I am sending IDOC from 4.6c to XI to ECC6.0 using IDOC Adapter. I want to ensure that IDOCs are processed serially(EOIO) on the receiver side. I tried setting up the SE16-->IDXQUEUE on XI for the Receiver system and enabled the Queue processing flag on the Receiver communication channel, but the IDOCs are not serialized.
I see that XI is using XBTO_007(EO) Queue. It should be using the queue that I specified in SE16.Please let me know what else needs to be done to implement EOIO for the IDOC adapter.
Please note Sender is 4.6c System while the receiver is ECC 6.0 on WAS>=6.2
Thanks in advance.
Rajeev Gupta

Rajeev,
From http://help.sap.com/saphelp_nw70/helpdata/en/bd/277264c3ddd44ea429af5e7d2c6e69/content.htm
<b>The receiver or sender system must be based on SAP Web Application Server 6.40 or higher.</b>
The blog listed above is when you need to sends Idoc from R3 to XI in EOIO. It does not work with SAP R3 4.6C for the reason above.
For sending Idoc's from XI to R3 ( to ECC in your case ) in EOIO, you need to seelct Queue Processing in the Receiver Idoc adapter and the rest I think is handled implicitly by XI.
Regards
Bhavesh
PS: Have not tried this practically though!
Message was edited by:
Bhavesh Kantilal

#'s coming up in IDOC when IDOC flatfile processed with RSEINB00

Hi,
We have given IDOCs in flatfile structure which are needed to be loaded in backend SAP R/3 through XI and it needs some transformation,so we are using XI for mapping in between,otherwise we would have processed directly into R3.
Basically we are placing IDOC Flatfile in a folder and we are running RSEINB00 program on XI through a file port in XI and IDOCS are getting created in Backend SAP R/3.
When we place IDOC flatfile in Windows folder and process the file we are getting #s in IDOC fileds(many fields) ,but we don't see any #s when we process the IDOC flatfile when placing IDOC flatfile on UNIX .Our XI/PI is running on UNIX.
please help,what causing the problem?
Thank you,
Regards,
Sathish

Hi Ravi kanth,
I see them (#s)in IDOC fields in backend SAP R/3 once the IDOC flatfile got processed.
as we are running RSEINB00 report on XI ,we noticed that empty tags are coming (from Windows OS Folder)in SXMB_MONI even before my mapping execution ,I think they are being populated as # in IDOC.but dont see this problem when IDOC file processed from UNIX folder.
You think ,if we save file in UTF-8 format or Binary might help rather than ANSI format and process it.
Thank you,
Sathish

IDOC Serialization Processing

Similar Messages

Maybe you are looking for