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

Similar Messages

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 Problem

Hi Experts,
We have a requirement where we need to send IDoc's to SAP PI in a sequence from SAP ECC and in the same sequence the Idoc should reach to the SAP PI.
We tried to do the sequencing through IDOC Serialization (From Mastering Idoc Business Scenarios BOOK), but the Idoc are not reached to MONI in the Same Sequence.
Please reply if anyone has done IDOC Serialization.
Regards,
Praveen Kalwa
Edited by: praveen kalwa on Jun 25, 2010 4:59 PM
Edited by: praveen kalwa on Jun 25, 2010 5:08 PM
Edited by: praveen kalwa on Jun 25, 2010 5:14 PM
Edited by: praveen kalwa on Jun 25, 2010 5:15 PM

Hi,
You can do the IDOC serialization in SAP PI by creating a queue .
The logic is, please create queue in PI which should be referred in SAP partner profile rule. We have implemeted this in our landscape which runs perfectly w/o any issues.
Please refer ht[/people/community.user/blog/2006/11/04/how-to-serialize-idoc-xml-messages-fed-into-xi|ht/people/community.user/blog/2006/11/04/how-to-serialize-idoc-xml-messages-fed-into-xi]

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

[svn] 1543: Bug: BLZ-152-lcds custom Date serialization issue - need to add java.io. Externalizable as the first type tested in AMF writeObject() functions

Revision: 1543
Author: [email protected]
Date: 2008-05-02 15:32:59 -0700 (Fri, 02 May 2008)
Log Message:
Bug: BLZ-152-lcds custom Date serialization issue - need to add java.io.Externalizable as the first type tested in AMF writeObject() functions
QA: Yes - please check that the fix is working with AMF3 and AMFX and you can turn on/off the fix with the config option.
Doc: No
Checkintests: Pass
Details: The problem in this case was that MyDate.as was serialized to MyDate.java on the server but on the way back, MyDate.java was serialized back to Date.as. As the bug suggests, added an Externalizable check in AMF writeObject functions. However, I didn't do this for AMF0Output as AMF0 does not support Externalizable. To be on the safe side, I also added legacy-externalizable option which is false by default but when it's true, it restores the current behavior.
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-152
Modified Paths:
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/endpoints/AbstractEndpoint.ja va
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/io/SerializationContext.java
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/io/amf/Amf3Output.java
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/io/amfx/AmfxOutput.java
blazeds/branches/3.0.x/resources/config/services-config.xml

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

HI can anybody   facing IDOC'S ISSUE

HI can anybody   facing IDOC'S ISSUE
SEND IT TO ME
I WILL SOLVE   FOR YOU
THANKS AND REGARDS
RAJU

hi there,
I am trying to load finsta into SAP from the middle ware GXS and all the ports in them looks good when I go to we02 to view the status, it gives error 51. the message says "Error during insert in table FEBKO". There are no more details of this error.
i Tried comparing FEBKO-AZIDT and FEBKO-WVTIM to make sure both are respectively unique
I have deleted this entries from FEBKO by running RFEBKA96 and then we tried to resend/reprocess the IDOC
but still persisting with the same error message 51,
the status on the idoc shud be 0 inorder to process that right.
even when we changed the time why is it giving us the error message 51.
can you put some light on to it please...
points will be assigned.
thanks
Jay

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,

File XI IDOC (Serialization )

Hi Experts
i have this scenario : A csv file is coming from the 3rd party and is converted into idoc at Pi and being updated in R/3 system.
i have been going through blogs, where i noticed "serialization " . what is meant by "serialization "? All the blogs were discussing the scenario as" IDOC > XI > FILE". For my scenario should we use the "serialization ".
thanx in advance

Hello...
Have you checked the replies in this thread:
When IDoc Serialization is required ?
>>All the blogs were discussing the scenario as" IDOC > XI > FILE". For my scenario should we use the "serialization ".
Your scenario is file to IDoc right? So if you are planning to create one file from one IDoc then no need of serialization (as each file will be creating only 1 idoc)
But if you want a single file to create multiple IDoc, then you may want to serialize the Entry of IDocs into ECC
Regards
Suraj

TESTING IDOC SERIALIZATION

Hi,
i want to test the idoc serialization . For that we send 2 idocs
-> In both IDOC Partner Profile we maintained the RULE(inturn attacted to Function Module and Gave Queue name).
For testing purpose we kept the error in the First IDOC so that 2nd IDOC gets Scheduled.
After sending two idocs in MONI when i check Queue that is generated for both the IDOCS is same But the Queueid is Different.
Why Queueids are Differently generated ...
Result : 2nd IDOC is Success ...(As per my requirement it must be Scheduled).
In MONI :
QUEUE/SEQUENCE - QUEUENAME(SAP_QUEUE). - Same for Both IDOCS.
QUEUEID - XBQOH__SAP_QUEUE - For First IDOC
QUEUEID - SAP_ALE_SAP_QUEUE - For Second IDOC

Providing a unique serialVersionUID obtained from serialver command to the Serilizable Class that is being serialized. So even if the Class structure changes a bit, the object is still eligible for Deserialization
Providing a readObject method for that Class
- When the Class is reconsituted with extra fields, that field in the Object to be deserialized will be intialized to default value. u can add class-specific intilization in this method.
- Also for small validation if neccessary
- Helps to handle some Compatible Changes: http://java.sun.com/j2se/1.4.1/docs/guide/serialization/spec/version.doc8.html

When IDoc Serialization is required ?

Hello,
IDoc's are serialized in master data distribution.
When IDoc serialization by IDoc adapter is required and also when ALE serialization of IDoc's is requried?
Is it necessary to tune on both of the above at the same time or any one?
In which scenario both serialzation technique is tuned on?
Please shed me some lights on this with business cases.
Regards,
Thiyagu

Hi,
Please check this link for example program.
http://help.sap.com/saphelp_nw04/helpdata/en/78/2175a751ce11d189570000e829fbbd/content.htm
Also, check out
Checkout
http://help.sap.com/saphelp_nw04/helpdata/en/0b/2a66d6507d11d18ee90000e8366fc2/content.htm
http://www.sapfans.com/forums/posting.php?mode=quote&p=383070&sid=3907f12b866299cc7e2e3e9728674ef3
Check if the above links helps...
Regards,
Swetha.

IDOC Serialization & Synchronous Scenarios with AAE

Hi Folks,
I have queries reg Advanced Adapter Engine (AAE):
1) Can we do the Synchronous scenarios through AAE.
2) How can i do the IDOC serialization. How AAE helps in that.
Am using PI 7.3 ...Can you please mention the possibilites for the above queries.
Thank you!!
Regards,
Sekhar

MDM Learn wrote:
Hi Folks,
>
> I have queries reg Advanced Adapter Engine (AAE):
>
> 1) Can we do the Synchronous scenarios through AAE.
Already supported as part of 7.1 / 7.11 so dont see any problem here
>
> 2) How can i do the IDOC serialization. How AAE helps in that.
>
> Am using PI 7.3 ...Can you please mention the possibilites for the above queries.
>
> Thank you!!
>
> Regards,
> Sekhar
the above should be very much supported if you are using the Java IDoc adapter. For serialization use qRFC in SAP partner profile

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

Similar Messages

Maybe you are looking for