Serialization of Z message type

Hi,
We have a Zprog  pulls the file from unix and creates the idocs.. it creates multiple types of idocs.  The message type is also customised(Z).
The issue is that when idocs are created, they are processed out of order causing the updates to assets to be out of sync.
My analysis is in the Zprog SERIAL field of  Control record is not filled with timestamp.
Will filling this SERIAL field will solve my issue?
Also coding help to populate the SERIAL in this format YYYYMMDD_HHMMSS
Any small or big clue is appreciated and rewarded.
Rhea.
Edited by: rhea on Oct 7, 2008 11:32 AM

Still looking for replies
one more clue we are using INBOUND_IDOC_PROCESS for creating idocs.
rhea.

Similar Messages

  • 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

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

  • PI IDOC Message Type Correlation for Customers & Addresses

    Hello
    We are struggling with an interface from MDM through PI and into ECC.  For example, PI grabs customer/vendor records from MDM and then sends them on to ECC.  In the process it creates IDOCS of two different message types (ADRMAS u2013 addresses, and DEBMAS u2013 for customer/vendor records)
    What is happening is that the Addresses and Customer/Vendor records are not being processed as logical units of work (LUW).  This is causing data synchronization issues in ECC where addresses are updated but customer master records are not.
    We are in desperate need of having two different IDOCS (ADRMAS and CREMAS) having related records between them be treated as logical units of work so that the related records are updated together.  If one portion fails it all should fail. 
    So far the team has not found good documentation on how to accomplish this in PI so that ECC can see that the IDOC records are related and to be treated as related LUWs. 
    Any help or references would be appreciated.

    hi,
    >>Getting idoc errors in production is a regular occurence in any system including production due to trouble with the data (bad zip codes, bad foreign keys, failures due to data validation routines, configuration changes that impact data structures).
    I know - that's when we can use WE02 and correct the wrong data
    >>There is SAP documentation that suggests that correlations/relationships can be established between idocs in PI and ECC (serialization), but we just don't quite understand it yet, and we are not confident that it will do for us what we need.
    no serialization will not do what you need as if the first one will be ok
    and second one not - serialization will not rollback the second one - sorry
    Regards,
    Michal Krawczyk
    http://mypigenie.com XI/PI FAQ

  • ALE - Status 52 Idocs for HRMD_A message type

    HRMD_A Idocs in target system are not completely posted, turning into status '52'. Most of the times the infotype 1001 idoc with relations ship P->S arrives before the idoc which has the actual objects(P, S) causing 'Relationship imposible because the object does not exist". We use program RBDAPP01 for inbound processing of Idoc which should take care of Serialization based on the time stamp of idoc creation in source system.
    Change pointors for Message type HRMD_A are processed using program RBDMIDOC in source system.
    It is unlikely that relationship P->S is created without object P being created in the source system. So the change pointors should create the idocs in the same sequence. But it is not happening.
    Any help on this appreciated.

    Hi Santosh,
    If you haven't found by now the .... here is the Solution:
    First change the size of table T77S0  check out note 305688
    Then process the IDOCS again - check out note 363187
    Regards
    Luis

  • Generate an additional iDoc message type when calling BD12

    How can a specific iDoc message type be generated (in addition to the other iDocs) when calling BD12 with specific output type?
    I would like that all iDocs belonging to one serialization group will be generated when calling BD12. is that possible?
    Thank you in advance,
    Asmaa

    Hi,
    Kinldy check the links which are useful to you.
    http://www.beinsoft.com/articles/sap-tutorial-ale-distribution-model2.php
    Thanks,
    Ramesh

  • Inutilização de NFe: Log de erro Message type 8 is not defined

    Olá Pessoal,
    Estamos com um erro aqui muito semelhante ao descrito na Thread: [Skip número da NF não autorizada|;.
    Solicitamos a inutilização de uma nota writer de saída que foi barrada no Monitor GRC por erro de validação e por isso estava com status 8 na J1BNFE (ECC). A inutilização foi feita com sucesso, o status no GRC está correto, mas no ECC a autorização ainda não constava. Executamos o report XNFE/UPDATE_ERP_STATUS_DIAL e ao fazermos a msg de "erro ao atuzalizar ECC". No monitor da J1BNFE a nota agora aparece com o seguinte log de erro:
    Message type 8 is not defined
    Message no. J1B_NFE018
    Diagnosis
    The messaging system passed a value for the message type to the back-end system (field I_MSGTYP) that is not defined in the back-end system.
    System Response
    The back-end system cannot interpret and process the inbound message.
    Procedure
    Configure the messaging system in a way that it transfers only allowed message types to the back-end system via the inbound interfaces J_1B_NFE_XML_IN or J_1B_NFE_XML_IN_TAB.
    Achei a thread mencionada acima com o mesmo erro e verifiquei a aplicação das notas, já que o problema foi solucionado com a aplicação das mesmas. Eis os status:
    Nota 1298283 (ECC) - Não relevante pois estamos no ECC 6.0 SP17;
    Nota 1376324 (ECC) - Não relevante pois estamos no ECC 6.0 SP17;
    Nota 1413636 (ECC) - Completely Implemented na SNOTE;
    Nota 1376901 (GRC) - Não relevante pois estamos no GRC SP13.
    Aparenmente alguma coisa ainda está faltando.. mas nao sei o que é.
    Desde já agradeço,
    Daniela Machado

    Verifique esses passos da nota 1298283 (no ECC)::
    Change Domain J_1BNFE_MESSAGE_TYPE
    Use transaction SE11
    Select Domain and insert name J_1BNFE_MESSAGE_TYPE
    Push Change.
    Select Tab "Value Range".
    Insert
    Fix value Short text
    8 Authorization to Skip a NF-e with Validation Error
    9 Rejection to Skip a NF-e with Validation Error
    Maintain table J_1BNFE_MAP_TYPE
    Use transaction SE16 and display the table entries.
    Push CREATE (F5)
    Insert records
    MSGTYP DOCSTA SCSSAT
    8 Space A
    9 Space B
    At.,
    Bernardo Braga
    Edited by: Bernardo Braga on Jul 1, 2010 10:06 PM

  • Message type BOMMAT (change BOM)

    Hello Guru,
    I have some question and need help, when i try a standard transaction CS02, try to change a BOM material existing for example, the base quantity of the BOM was 650, i enter new data as 655, but suddenly retain the original Qty as 650 and save the changes as SAP will accept the changes i've done (BOM for material 2456 changed) but eventual i have not change any value to the original BOM. SO it mean this is standard SAP funtionality for CS02.
    But when we use an interface using message type BOMMAT a standard SAP message tpye, we have created an IDOC using this message type and same data as the original was maintain to it, to be more exact we plan to change a BOM thru this IDOC but all the data we have is the same value of the original BOM, so we expect no error could be encounter of this IDOC since in standard CS02, changing of BOM even same value was inidicated did not had error message encountered when saving.
    But thru our process, when we try to process the IDOC with message type BOMMAT in program RBDAPP01 (BD20) the idoc did not pass it when into status 51(Error when saving BOM. Please see the application log.) and when we check the BOM it has duplicate value upon executing the program we able to fix it when we delete the duplicate line segment in the IDOC and reprocess it once again.
    my question is why in standard message type BOMMAT had encountered error when processing when we try to make change of BOM even the same value is carried out by the IDOC, and why in standard CS02 saving a change of BOm with same value as it is SAP accept the process? Please help and clear the process.
    Any inputs R.Brahamankar and Vivek
    Thanks
    Edited by: Ryan on Feb 9, 2009 9:23 AM

    BOMMAT  and process code BOMM

  • Idoc and message type not getting replicated in the receiver system

    Hi
    i have created a Z Idoc and didtributed the mode from system A ....I can see the distribution model in system B
    However i cannot see the custom zidoc / message type in sys B.. Do i need to create the zidoc again in sys B

    Hi Tarang,
    at least ou need the required partner agreements and you should have a processing function for inbound IDoc. To implement this, the full definition of IDoc including Segment definition should be present in receiving system.
    Just look at standard IDocs and do as they do.
    Regards,
    Clemens

  • Idoc message type for open orders & Open JIT lines

    Hi,
    I need to send Open Purchase Order data and Open JIT lines data to supplier daily via Idocs.
    Is there any standard messege type available for this data.
    Regards

    Hi Rohita,
    Instead of changing the standard domain, You have to make the changes in the User Exit.
    Say Qualifier 001,002,003 were already there in the domain.
    001--Purchase Date
    002--Delivery Date
    003--Ordered Date
    In the user exit u have to just add the segment and the qualifier without making any changes to the Standard Domain.
    These Qualifiers are just like other variables and u can add whatever values to them that u want..
    You can add Qualifier 004 for Trnasportation Date or Goods issue date and have to communicate the MiddleWare informing that date with this Qualifier will be Transportation Date and they will do the mapping to the corresponding field in other syste.
    You can have as many message types as u want for the same IDoc type. There is no harm in having multiple message type. And u dont need to change the standard domain. It can be done without changing the domain.
    If u analyse the FM closely u will realise that they have done coding for those values in the domain.
    So instead of adding it to domain u just have to do the coding for this new qualifier.
    Revert back if u need any help on it.
    Thanks...
    Message was edited by:
            Utsah Garg

  • How to connect our outbound function module to the message type

    how to connect our outbound function module to the message type any transcation code exits to assign the message type with the function module .
    Thank in advance .
    A. Thiru

    Hi Thiru,
    Standard Transaction Codes, have their own Function Modules for generating Outbound/Indbound Idocs. Where these Function Modules will be configured to a particular Process Codes.
    For E.g for PO's
    Process code : ME10 - IDOC_OUTPUT_ORDERS - for creation
    In case if its a Z Function Module, It depends on the case how you use IDOC types. either directly through Z Program or through Inbound/Outbound Process  codes with respective Function modules.
    Regards,
    Anbalagan

  • IDOC Message type for open sales orders

    Hi
    We are trying to send the list of open sales orders of a customer in an IDOC to the customer. For example, if the customer has got 15 sales order to be delivered to him , he needs the details of all these 15 orders in an single IDOC
    Is there any message type available for this in SAP R/3 4.7 version
    Regards
    Anandh

    Try VA05 schedule lines standar variant...include status fields and both ordered qty and confirmed qty. In SAP standard system order status, status A means open orders fully (Nothing shipped, everything opened). Status B means in process orders (Partially processed - shipped). Status C means complete orders (Nothing opened). As there is no delivered qty in VA05,  you need to download to excel the file and calculate the difference between both qty fields for each A and B status. That is a way to get the missing qty to be delivered or open qty as you stated.
    Hope it helps.
    Jorge Fernandez

  • Change sales orders using ORDCHG Message type

    Hi,
    I am trying to test the changing of quantity on sales order items using message type ORDCHG and process code ORDC. In segment E1EDP01 the action code is set to 002 - item changes. However when the IDoc is posted a new line is created in the order rather than the existing one being changed. The action code in the header is set to 003 - one or more items changed. Does anybody know how to control the change of quantity for an existing item?
    Many Thanks
    Caroline

    Hi,
    Try to populate Logical message code 'CHG' in the EDIDC-MESCOD while you are creating the IDoc.
    If a message code has been entered in the (inbound) partner profiles, the external system must fill the field during IDoc inbound processing.
    Regards,
    Yogesh

  • Idoc Message type for Scheduling agreement

    Dear Experts,
    How to configure to create Idoc for Scheduling agreement (not the releaseed schedule lines) ?
    I am trying to use message type ORDERS05 but it is not working.
    Will any body guide me preferably step by step process for this ?
    Thanks in Advance,
    Best Regards,
    Raju

    Hi Anji,
    Thanks for the Reply. But i think ORDRSP is for Order Confirmations.
    But I have to send Outbound Idoc for a Schedule Agreement.
    Whether the same  Idoc type & Messge type used for SO/PO(e.g ORDERS05, ORDERS/ORDCHG) can be used for Scheduling Agreement.
    Please Advice.
    Regards,
    Anbalagan

  • Message type for Scheduling Agreement - Outbound IDoc

    Hi All,
    I have to create an Idoc for Scheduling Agreement through a Z program based on some conditions. I have bit confusion, whether i can use Idoc type for Orders(e.g ORDERS01..05) & Message type ORDERS / ORDCHG to generate Outbound Idoc.
    Already there is process code for for ORDCHG mappig IDOC_OUTPUT_ORDCHG & ORDERS mappig IDOC_OUTPUT_ORDERS.  Whether there will be any impact on this.
    Appreciate your help.
    Regards,
    Anbalagan.

    Hi Anji,
    Thanks for the Reply. But i think ORDRSP is for Order Confirmations.
    But I have to send Outbound Idoc for a Schedule Agreement.
    Whether the same  Idoc type & Messge type used for SO/PO(e.g ORDERS05, ORDERS/ORDCHG) can be used for Scheduling Agreement.
    Please Advice.
    Regards,
    Anbalagan

Maybe you are looking for

  • How do you get your ringtone that you bought on your iPad to your Iphone

    I bought several ringtones on my iPad because its a lot faster and I thought it would automatically sync to my iPhone like all my songs. But now I can't find the ringtones anywhere except my iPad sounds. It's not in my purchases or in my iCloud. Idk

  • I can't import my cds onto itunes

    whenever i import my cds onto itunes.... the songs are all messed up and i'm pretty sure that my cds aren't the problem... the time for the songs are all messed up.... for example... one of the song's time would be 798:4354523948595 and i no that tha

  • Itunes doesn't start automatically

    Any reason why my iTunes does not open automatically once the iPod is plugged in? I do have the settings Open Itunes when Ipod connected checked. Thanks.

  • Recipient error. : CrystalEnterprise.Smtp

    Hi, am getting this 'recipient error. : CrystalEnterprise.Smtp' error in a Business Object Crystal report. I am able to send mail to the recipients but the report status is fail. The report was running fine for a while and now it is giving this error

  • What is the proper address to file a complaint with Verizon Wireless?

    As far as I am concerned, I have been lied to 3 times by various members of this company.  I need an address to write to where someone has the DIRECT AUTHORITY to remove fraudulent contracts placed on my account.  I will provide all the written docum