Serialization in SAP R/3

Dear all,
In one of the interface flow, we are expecting a batch of  IDOCs from SAP R/3 in a serial order, which is not happening right now.
I want to know, if there is a option/function module to enable serialization from SAP R/3.
Kindly pour in your comments.
Regards,
Younus

This could help you...
/people/community.user/blog/2006/11/04/how-to-serialize-idoc-xml-messages-fed-into-xi
http://help.sap.com/saphelp_erp2004/helpdata/en/bd/277264c3ddd44ea429af5e7d2c6e69/content.htm
http://help.sap.com/saphelp_erp2004/helpdata/en/0b/2a66d6507d11d18ee90000e8366fc2/content.htm
/people/sap.user72/blog/2005/01/28/setting-up-inbound-qrfc-queues-for-serializing-idocs-using-the-idoc-adapter

Similar Messages

  • Serialization in SAP 4.6C

    Hello,
    is there a standard way to serialize ABAP Objects in SAP4.6C ? The interface IF_SERIALIZABLE_OBJECT does not exist, nor does the "CALL TRANSFORMATION"...
    If there is no standard way, does anybody know about some other way to serialize AO in that release?
    Regards,
    Björn

    Hello,
    does anybody have an idea, knowledge of some SAP technique or even a link to an existing project?
    Björn

  • Nuclear Industry use of SAP item serialization/bar coding/(Gen2) RFID)

    Does anyone have a link to any article(s) or journal(s) - preferably online -  that have information on nuclear industry companies using serialization in SAP with/without bar coding or (Gen 2) RFID?  I'm doing research on industries that do this and I'm looking for such info on nuclear industry companies; this could be companies that make nuclear devices, nuclear plants, etc...   Supposedly, there are many nuclear industry companies that use serialization but I haven't found any articles online.  Thanks.

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

  • 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]

  • RMA and Serialization

    Hi Friends,
    I will be grateful to you if anybody give details about the RMA (Return Material Authorization) and how to configure in SAP. I did not find anything in the past thread.
    Also please help me in understanding the Serialization in SAP and how to configure it.
    Thanks,
    Jans

    Hello,
    After the sales , if the customer complains about the product, some companies offer repair. In repair process, a repair notification will be created, followed by a repair order. The material will be received in to the stores with reference to the repair order (Return delivery). Once checked, the repair process starts, creating a service order, issuing spares to the order, confirm material and labour and technically complete the service order. Once all these are completed, the goods will be given back to the customer (outbound delivery). The repair charges will be paid by the customer according to the agreement.
    We need to create a serial number profile and a serialisation procedure will be assigned to the serial number profile. The we set the rule of serial number checking, whther it is mandatory in the case of order/quotation or at the time of delivery.
    Prase

  • Equipment Master and Serialization

    Hi,
    Can anybody give me an overview/Definition on Equpment master and serialization in SAP. Where do we need them exactly and why? how does it relates to SD?
    Your early response will be highly appreciated.
    Thanks

    Hi Muhammad,
    Please check this links.
    http://help.sap.com/saphelp_erp2005/helpdata/en/01/d544ef4ab311d189740000e8322d00/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/dd/560d93545a11d1a7020000e829fd11/frameset.htm
    Hope this will help.
    Regards,
    Ferry Lianto
    Please reward points if helpful.

  • What is mass-serialization ?

    What is mass-serialization  in SAP AUTO ID ?
    how is that related to Consumer goods and pharma company.

    Hello PSRK,
    Mass Serialization is a conceptual term which is not tangibily present in SAP Auto ID but it can be said as a thing which can be achieved using SAP Auto ID Infrastructure.
    Mass Serialization actually means giving unique numbers to each item/case/pallet so that it can be uniquley identified in large numbers. Meaning i have tagged 100 consumer items at one time to identify them uniquely. This number in RFID terms is called EPC - Electronic Product Code
    EPC - in consumer goods or pharma industry will have an encoding type.  The encoding type is
    GTIN _ Global Trade Identification number at item level (eg. coke bottle)
    SSCC _ Serial Shipping Container Code (eg coke case/coke pallets)
    EPC = Encdoing Type + Serial Number makes us identify an item uniquely across the globe
    GTIN or SSCC identifies a particular organization and its particular product
    GTIN = Company Code + Asset Type
    SAP Auto ID lets us generate this EPC numbers and encode this numbers onto RFID tags/ 1-D Barcodes/ 2-D Barcodes etc and these tags are applied on products/cases/pallets
    This whole concept is called Mass Serialization.
    Please revert for other questions
    Thnks and Regards

  • JDBC sender adapter issue

    Hi SDNers,
    I have a scenario which picks data from AS400 table using JDBC adapter.
    My sample SQL query and update query are as follows
    SQL query : Select * from <table> where <keyfield> = min(keyfield) and flag ="";
    Update query: Update <table> set flag = "true" where <keyfield> = min(keyfield) and flag ="";
    This is to ensure records are processed one by one.
    All goes well. Suddenly I have a issue where out of "n" records in the table one record failed to reach the target system. My cause of concern is there is no error in RWB and SXMB_MONI.
    I have identified the missing record and could see the flag has been set to "true" in the table. I dont have TREX installed in XI, so could not track the message in XI.
    Has any one faced this issue? Any ideas are highly appreciated.
    Regards,
    Jai Shankar

    Hi All,
    It seems, still the issue is not solved. We have the same issue again inspite of setting the transaction isolation level to serializable.
    SAP Note says
    <i>The SELECT and the UPDATE are run in the same DB transaction,
    i.e. both statements have the same view on the database.
    Make sure that both statements use the same WHERE clause. An
    additional requirement for the correct operation of this scenario
    is the configuration of an appropriate transaction isolation level
    on the database (i.e., repeatable_read or serializable). You might
    also consider using a "SELECT FOR UPDATE" statement instead of a
    plain SELECT statement to ensure proper locking on the database</i>
    We have ensured
    a. Same where clause.
    b. Serializable transaction isolation level
    Am not much sure how SELECT FOR UPDATE works. We are using AS400 db.
    Any experience with SELECT FOR UPDATE.
    Regards,
    Jai Shankar

  • Differences between LIS & LO

    Hi everyone,
    can anybody tell me the differences between LIS & LO's
    Thank u all

    Hi Shaik,
    Please search the forum before post query on forum. That is helpful to you as well as to your friends in forum. Please dont waste the other time.
    And refer the following threads...
    LIS &LO
    Refer the blogs by roberto: (Most useful)
    https://www.sdn.sap.com/sdn/weblogs.sdn?blog=/pub/u/21406 [original link is broken] [original link is broken] [original link is broken]
    LOGISTIC COCKPIT DELTA MECHANISM - Episode one: V3 Update, the ‘serializer’
    /people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146
    LOGISTIC COCKPIT DELTA MECHANISM - Episode two: V3 Update, when some problems can occur...
    /people/sap.user72/blog/2004/12/23/logistic-cockpit-delta-mechanism--episode-two-v3-update-when-some-problems-can-occur
    LOGISTIC COCKPIT DELTA MECHANISM - Episode three: the new update methods
    /people/sap.user72/blog/2005/01/19/logistic-cockpit-delta-mechanism--episode-three-the-new-update-methods
    LOGISTIC COCKPIT - WHEN YOU NEED MORE - First option: enhance it !
    /people/sap.user72/blog/2005/02/14/logistic-cockpit--when-you-need-more--first-option-enhance-it
    Regards,
    BVC

  • Can anyone explain briefly  What is LIS and LO?

    hai sapbw-gurus,
    Can anyone explain briefly  What is LIS and LO?
    what is the different b/w LIS and LO?
    how u will create these two in sap bw?

    hi,
      LIS is old technique through which we can load the data. Here we use typical delta and full up-loading techniques to get data from an logistics application, it uses V1 and V2 update, it means that it was a synchronous or asynchronous update from the application documents to LIS structures at the time when the application document was posted.
    LO Cockpit is new technique i think from bw 3.0 ( i am not sure) which uses V3 which is an update that you can schedule, so it does not update at the time when you process the application documents, but it will be posted at a later stage.
    Another big difference between LO and LIS is that,
    You have separate datasources for header level, item level and schedule line level available in LO, you can choose at which level you want to extract your data and switch off others, which results in reduced data.
    we do not have this flexibility with LIS structures
    with Plug-In 2001.2 S2xx-Structures have been replaced by Logistics Extraction Cockpit. However, R/3 releases 4.x support S2xx-Structures and Logistics Extraction Cockpit in parallel.
    With new LBWE extractors there are a lot of benefits:
    - Detailed Extraction: extraction can be deactivated (e.g. Schedule Line Data) leads to leaner extractors with less volume.
    Document Changes: only BW-relevant data changes will be updated (less upload volume).
    - LIS-Tables are not updated reduced data volume due to avoided redundancy.
    - Update with Batch-Process (V3) -> no load on daily business (but now there are available different delta methods as the direct delta...)
    - No LIS-Know How necessary.
    - Functional Enhancements easy to be done.
    - Central, uniform maintenance tool for logistics applications (LBWE)
    - No Delta-Tables (SnnnBIW1/-2) no double update, no double Data-Storage
    - A lot of flows are covered: Purchasing,Inventory Controlling, Shop Floor Control, Quality Management, Shipment, Sales, Shipping, Billing, Plant Maintenance, Customer Service, Retailing....
    LOGISTIC COCKPIT DELTA MECHANISM - Episode one: V3 Update, the ‘serializer’
    /people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146
    LOGISTIC COCKPIT DELTA MECHANISM - Episode two: V3 Update, when some problems can occur...
    /people/sap.user72/blog/2004/12/23/logistic-cockpit-delta-mechanism--episode-two-v3-update-when-some-problems-can-occur
    LOGISTIC COCKPIT DELTA MECHANISM - Episode three: the new update methods
    /people/sap.user72/blog/2005/01/19/logistic-cockpit-delta-mechanism--episode-three-the-new-update-methods
    LOGISTIC COCKPIT - WHEN YOU NEED MORE - First option: enhance it !
    /people/sap.user72/blog/2005/02/14/logistic-cockpit--when-you-need-more--first-option-enhance-it
    differences between LO and LIS
    hope it helps,
    regards,
    partha

  • LIS (Extract Structure to Datasource) Documentation

    Hi
    Does anyone have any good documents that explain the relationship with the LIS and the extract structures etc.
    I understand that they are predefined Extract structure from (LIS) and if you add more fields then you must do ABAP too to make sure these are filled.
    As per my post yesterday I originally thought that as the fields were in the main table in SAP anyway then it would just be a case of just adding them to the extract strucuture in SBIW.
    This now seems worng
    Any documentation is very welcomed.

    Very good weblogs on LOGISTIC COCKPIT DELTA MECHANISM from “Master” Roberto Negro:
    Episode one: V3 Update, the ‘serializer’
    /people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146
    Episode two: V3 Update, when some problems can occur...
    /people/sap.user72/blog/2004/12/23/logistic-cockpit-delta-mechanism--episode-two-v3-update-when-some-problems-can-occur
    Episode three: the new update methods
    /people/sap.user72/blog/2005/01/19/logistic-cockpit-delta-mechanism--episode-three-the-new-update-methods
    WHEN YOU NEED MORE - First option: enhance it
    /people/sap.user72/blog/2005/02/14/logistic-cockpit--when-you-need-more--first-option-enhance-it
    Related to changes the data source extractor when a delta load is in production:
    How to retain deltas when you change LO extractor in Production system
    /people/pradip.patil/blog/2006/06/07/how-to-retain-deltas-when-you-change-lo-extractor-in-production-system
    Regards,
    Sergio

  • Drawbacks of LIS  compare to LO

    Hi  friends,
       could u plz give me the drawbacks of LIS   compare to LO Extraction.. and when we go for LO....
    REGARDS
    AJAY

    hi
    LIS is old technique through which we can load the  data. Here we use typical delta and full up-loading techniques to get data from an logistics application, it uses V1 and V2 update, it means that it was a synchronous or asynchronous update from the application documents to LIS structures at the time when the application document was posted.
    LO Cockpit is new technique i think from bw 3.0 ( i am not sure) which uses V3 which is an update that you can schedule, so it does not update at the time when you process the application documents, but it will be posted at a later stage.
    Another big difference between LO and LIS is that,
    You have separate datasources for header level, item level and schedule line level available in LO, you can choose at which level you want to extract your data and switch off others, which results in reduced data.
    we do not have this flexibility with LIS structures
    with Plug-In 2001.2 S2xx-Structures have been replaced by Logistics Extraction Cockpit. However, R/3 releases 4.x support S2xx-Structures and Logistics Extraction Cockpit in parallel.
    With new LBWE extractors there are a lot of benefits:
    - Detailed Extraction: extraction can be deactivated (e.g. Schedule Line Data) leads to leaner extractors with less volume.
    Document Changes: only BW-relevant data changes will be updated (less upload volume).
    - LIS-Tables are not updated reduced data volume due to avoided redundancy.
    - Update with Batch-Process (V3) -> no load on daily business (but now there are available different delta methods as the direct delta...)
    - No LIS-Know How necessary.
    - Functional Enhancements easy to be done.
    - Central, uniform maintenance tool for logistics applications (LBWE)
    - No Delta-Tables (SnnnBIW1/-2) no double update, no double Data-Storage
    - A lot of flows are covered: Purchasing,Inventory Controlling, Shop Floor Control, Quality Management, Shipment, Sales, Shipping, Billing, Plant Maintenance, Customer Service, Retailing....
    LOGISTIC COCKPIT DELTA MECHANISM - Episode one: V3 Update, the ‘serializer’
    /people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146
    LOGISTIC COCKPIT DELTA MECHANISM - Episode two: V3 Update, when some problems can occur...
    /people/sap.user72/blog/2004/12/23/logistic-cockpit-delta-mechanism--episode-two-v3-update-when-some-problems-can-occur
    LOGISTIC COCKPIT DELTA MECHANISM - Episode three: the new update methods
    /people/sap.user72/blog/2005/01/19/logistic-cockpit-delta-mechanism--episode-three-the-new-update-methods
    LOGISTIC COCKPIT - WHEN YOU NEED MORE - First option: enhance it !
    /people/sap.user72/blog/2005/02/14/logistic-cockpit--when-you-need-more--first-option-enhance-it
    differences between LO and LIS

  • LIS VS LO

    Hi gurus,
          please tellme What is Difference b/n LIS  & LO?
               ThanQ.
       Regards,
       Ramesh.

    hi
    LIS is old technique through which we can load the data. Here we use typical delta and full up-loading techniques to get data from an logistics application, it uses V1 and V2 update, it means that it was a synchronous or asynchronous update from the application documents to LIS structures at the time when the application document was posted.
    LO Cockpit is new technique i think from bw 3.0 ( i am not sure) which uses V3 which is an update that you can schedule, so it does not update at the time when you process the application documents, but it will be posted at a later stage.
    Another big difference between LO and LIS is that,
    You have separate datasources for header level, item level and schedule line level available in LO, you can choose at which level you want to extract your data and switch off others, which results in reduced data.
    we do not have this flexibility with LIS structures
    with Plug-In 2001.2 S2xx-Structures have been replaced by Logistics Extraction Cockpit. However, R/3 releases 4.x support S2xx-Structures and Logistics Extraction Cockpit in parallel.
    With new LBWE extractors there are a lot of benefits:
    - Detailed Extraction: extraction can be deactivated (e.g. Schedule Line Data) leads to leaner extractors with less volume.
    Document Changes: only BW-relevant data changes will be updated (less upload volume).
    - LIS-Tables are not updated reduced data volume due to avoided redundancy.
    - Update with Batch-Process (V3) -> no load on daily business (but now there are available different delta methods as the direct delta...)
    - No LIS-Know How necessary.
    - Functional Enhancements easy to be done.
    - Central, uniform maintenance tool for logistics applications (LBWE)
    - No Delta-Tables (SnnnBIW1/-2) no double update, no double Data-Storage
    - A lot of flows are covered: Purchasing,Inventory Controlling, Shop Floor Control, Quality Management, Shipment, Sales, Shipping, Billing, Plant Maintenance, Customer Service, Retailing....
    LOGISTIC COCKPIT DELTA MECHANISM - Episode one: V3 Update, the ‘serializer’
    /people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146
    LOGISTIC COCKPIT DELTA MECHANISM - Episode two: V3 Update, when some problems can occur...
    /people/sap.user72/blog/2004/12/23/logistic-cockpit-delta-mechanism--episode-two-v3-update-when-some-problems-can-occur
    LOGISTIC COCKPIT DELTA MECHANISM - Episode three: the new update methods
    /people/sap.user72/blog/2005/01/19/logistic-cockpit-delta-mechanism--episode-three-the-new-update-methods
    LOGISTIC COCKPIT - WHEN YOU NEED MORE - First option: enhance it !
    /people/sap.user72/blog/2005/02/14/logistic-cockpit--when-you-need-more--first-option-enhance-it
    differences between LO and LIS
    hope it helps.
    cheers.

  • Serialize IDOCs PI to SAP Backend

    HI,
    I need to serialize IDocs thats PI send to a sap backend system.
    rigth now we have one CC with max connection = 1 but it is not enough.
    but something is not clear at all for me.
    I need to send IDocs with QoS EOIO so, i asume that checking the parameter "Queue Processing" in the IDoc Receiver Channel the IDocs will sen them to SAP in EOIO, but that means --> One queue will be defined(in backend) for each IDoc that use this Channel?.
    If i set this functionality could i increase the parameter max connection to 10( for example) and the channel should know which queue was defined for each IDoc in the backend or it is not possible and I am thinking crazy things.
    Is it possible also to configure the transaction IDXQUEUE in SAP Backend?
    Best Regards.

    Searching for othar alternatives y found that is possible to change the QoS or the Queue id values in a Messager Mapping.
    Change Queue name in Message mapping
    http://help.sap.com/saphelp_nw04/helpdata/en/6e/ff0bf75772457b863ef5d99bc92404/frameset.htm
    but as i can see, there is not possible to access the variables QUEUE_ID and QUALITY_OF_SERVICE since those are ReliableMessaging's variables(help.sap link above)
    so i can access all Main's variables like SENDER_SERVICE, MESSAGE_ID, etc etc)
    How can i get access to this ReliableMessaging's variables from UDF or Adapter Module?
    In the thread above someone mentions that was not able to modify those values in a UDF but in a Adapter Module (i asume using the same code below) what could be the difference accessing frmo UDF o Adapter Module?
    UDF Code
    java.util.Map map;
    DynamicConfiguration conf = (DynamicConfiguration)container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
    DynamicConfigurationKey qos = DynamicConfigurationKey.create("http://sap.com/xi/XI/System","QUALITY_OF_SERVICE");
    conf.put(qos,"EOIO");
    DynamicConfigurationKey key = DynamicConfigurationKey.create("http://sap.com/xi/XI/System","QUEUE_ID");
    conf.put(key,queueName);
    return "";

Maybe you are looking for