ACC_DOCUMENT02 idoc inbound status 51

Hi!
I have this message error.
Diagnosis
A balance has occurred in transaction currency 'SEK' with the following details:
Exchange rate '00', amount '        12.000,00' and currency key 'SEK'.
The data in the transaction currency were transferred from the calling application.
System response
Your data cannot be processed in FI.
Procedure
The error is probably in the calling application.
i have 6 E1BPACCR09 segments with currency = SEK and AMT_DOCURR. The sum of AMT_DOCURR in all six segments are 12000 (like error)
Inbound process execute BAPI_ACC_DOCUMENT_POST
Can u help me?
Regards

Hi,
use <b>we19</b> and debugging to analyse.
Reward points
Regards

Similar Messages

  • EDI idoc inbound statuses

    We're running SAP in a different partition from EDI (TrustedLink) on an iSeries.  I'm getting inbound documents just fine, but no inbound statuses.  I see that the status documents make it over to the SAP partition but they're not visible in WE05 - so all of my successful outbound 850s are at at status of 18 & that's it.  I've looked at authorities etc but am still missing something.  Thanks in advance if anyone can point me in the right direction.  Susan

    try this
    enter tcode we21,
    Go to system , click on status
    Then you can see the programe name , Double click on programe name, you can see ABAP editior screen.
    Then you can see go to tan and click on object directry Tab.
    You can see package for which object is created.
    Now use tocde Smod, select F4 for enchancement , in package you can enter SED.
    You can get follwing user exit
    Exit name Short text
    SIDOC001 Customer function for module pool EDI1
    SIDOC002 CA-EDI: Exits in Function Group EDI6 (Partner Profile)
    Technically all EDI-IDOC inbound and outbound programs are wirtten as FUCNTION MODUELS.In the every fucntion moudle you can find large number of user-exits.For outbound idoc after filling every segment you have a user exit like CALL CUSTOMER FUNCITON '001'.You can find by using the keyword search CALL CUSTOMER FUNCITON in that funciton module.
    In inbound also you can find after every segment you can find user-exit.
    For funciton module search you can search in se37 by using idoc type,For example ORDERS01 search in se37 by using *ORDERS8.
    regards,
    sapsd

  • Inbound IDOC error - status code 52- application document not fully posted

    Hi,
       In Inbound IDOC, the status code is 52 ---> Application document is not fully posted(satus of the inbound idoc is in yello colour). I want to reprocess this idoc in BD87 t.code in order to convert the yellow colour to green colour. Before reprocessing the IDOC, i need to rectify the problem and then reprocess the idoc in bd87. am i correct? if yes, what i need to do to solve the error --->application document not fully posted. Please guide me friends.
    Thanks in advance.
    Regards,
    Sri

    HI
    If you are FM to process the inbound  IDOC,
    possibilities are like below .
    Reason 1 :
    In partner profiles, check is it trigger immediately or not ? for particular partner profile which u r using .
    reason 2 :
    If you are using BDC code to update the data .if any screen contains error then also you will get the status in yellow .
    reason 3 :
    Have you tried with  TCODE  BD87 ,  might be it is processing error also .
    i have worked on same probelm so  if u r not solved with the issue after trying above 3 reasons .
    reply me back .

  • Inbound Processing of Idocs with status other than success

    Hi,
           I am new to ALE/Idocs. Can anyone  please let me know how can I process the Idocs which have the status other than 53.
    Thanks &  Regards,
    Indira

    Hi,
    In addition to the previous posts few more programs to process failed inbound IDocs are as mentioned below.
    - Use program RBDAGAIE to process edited IDocs (IDocs with status 69)
    - Use program RBDAPP01 to process IDocs failing with serialization issue (IDocs with status 66)
    - Use program RBDAGAI2 to process IDocs after ALE inbound error (IDocs with status 56, 61, 63, 65)
    ~ Bineah

  • IDoc - Inbound delivery

    Hi Experts,
    Inbound EDI message order acknowledgments:
    When we cancel a purchase order item with IDoc message 'ORDRSP', this leads to an error message in the IDoc inbound processing.
    There is note 890812, but i guess it is till release 5.0
    Can anybody please guide me for the solution.
    Thanks,
    Sourabh Kothari

    Hi Experts,
    When we tested for the note, it is giving the status that this cannot be implemented.
    Could any one give me the alternate solution for the IDoc inbound processing.
    When the vendor sends the quantity 0 against any of the line items, the other line items are also not posted. There error message is ME794.
    As per the above note implementing the corrections & when the item is deleted in PO, again processing the idoc would be successful. But the note is not valid for ECC 6.0
    Please guide.
    Thanks,
    Sourabh Kothari

  • Need IDOC inbound and outbound programs

    hi,
    i am new to xi.
    i want IDOCs , inbound and outbound / function module  programs for    PURCHASE ORDER
    and GOODS RECEIPT.
    ex:  BD10 for material master (matmas01).
    thanks and regards
    v ijender

    for purchase order.
    ORDERS / ORDERS04
    ORDCHG / ORDERS04
    ORDRSP / ORDERS04
    Programs
    RBDMIDOC – Creating IDoc Type from Change Pointers
    RSEOUT00 – Process all selected IDocs (EDI)
    RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
    RSARFCEX - Execute Calls Not Yet Executed
    RBDMOIND - Status Conversion with Successful tRFC Execution
    RBDMANIN - Start error handling for non-posted IDocs
    RBDSTATE - Send Audit Confirmations
    FOr testing you can use WE19.
    and also check the below link
    http://www.erpgenie.com/sapedi/message_types_masterdata.htm
    regards
    kummari

  • SAP IDOC shows status 03, but no file is written

    We have SAP configured to generate delivery IDOCs when the SAP Delivery document is posted/saved. The IDOC is initially created with status 30. There is batch job RSEOUT00 every 30 mins that collects the IDOCs in status 30 and converts to status 03. When we review the IDOC processing screen, even though they are in status 03 and successfully written outside of SAP to a folder, there is no file in the folder. We are missing IDOCs. There is no real time external system integration. We are simply trying to write IDOC files to a folder.
    Can you some please share your insights on how to resolve this issue?
    Thanks in advance
    Satish

    RFC destinations, Logical systems, and then Partner profiles needs to be maintained. and You need to create the Distribution model  in sender system.
    Partner profiles maintained in both the systems, soure Outbound properties
    Target Inbound properties.
    if you have two clients in system it will be easily you can check.

  • *IDOC INBOUND ( NON SAP system - SAP system )*

    I am transferring IDOC  INBOUND ( NON SAP system ->> SAP system ) by calling SAP standard funtc module IDOC_INBOUND_SINGLE using SAP JCo.
    In which I am passing all necessary information in Control Record regarding sender and receiver port/IDOC/segment etc.
    BUT help me to clarify my doubt that if i am calling a function and i am able to access SAP FM, then why i have to specify the SAP port/RFC connection at RECEIVER end in WE21.
    Whats the Significance if i am calling the FM from same SAP system and configuring the port explicitly in WE21.*
    If i don't Specify in we02 i am getting error as EDI : RECEIVER PORT in CONTROL RECORD is INVALID

    Dear Sree,
    For Basic understanding of IDOC read : saptechnical - Step-by Step ALE IDOC guide ( all necessary TCodes available here )
    Kindly let me know your data flow .
    In short :
    As per my scenario the data flow is from  non SAP to SAP  i,.e. Inbound processing.
    At my non SAP  i am calling SAP standard function IDOC_INBOUND_SINGLE using SAP Jco 2.1.
    You have to fill all Control Structure EDI_DC40 ( port etc. ) and Table parameter EDI_DD40 ( segment etc. )
    Read IDOC status and error in WE02.
    Goodluck.
    - Aakash

  • Outbound IDoc Error: Status Code 37  'Sender Port' is invalid

    Hi
    I have an Error when the Outbound IDoc is triggered.
    It shows that 'Sender Port in Control Record is invalid'.
    Status Code: 37.
    I know that there are some issues with the Sender Port Definition.
    Please help me out to solve this problem using some checkpoints at each and every step.
    Reward Points Assured.
    Regards,
    Baburaj

    Hi Baburaj Manickam
    Good
    Follow this simple procedure
    1) Send an outbound IDOC data(MATMAS) to a flat file on client1(SENDER).
    -  Create File Port (WE21) for outbound file.
    -  Maintain Distribution Model (BD64) for sender ->receiver system.
    -  Create Partner Profile (WE20) for logical system.
    -  You can use this program RBDSEMAT (t/code BD10) to generate IDoc MATMAS file(s). 
    _  Then you can FTP the file(s) to receiver system.
    2) Upload the flat file as an IDOC on the inbound sytem
    which is Client2(RECIEVER).
    -  Create File Port (WE21) for inbound file.
    -  Maintain Distribution Model (BD64) for receiver -> sender system.
    -  Create Partner Profile (WE20) for logical system.
    -  You can use this program RSEINB00 to upload IDoc MATMAS file(s). 
    INBOUND IDOC PROCESSING:
    Firstly attach your idoc to a process code.
    In the process cod you can tell the system that the specified program should be triggered whenever an idoc of that type comes to the system.
    Then you want to have a Z-function module for your idoc processing, if I understand correctly.The steps should be:
    1. Create a z function module for idoc inbound posting (copy from a function module idoc_input_*).
    2. Set Function Modules as Inbound: - Transaction BD51
    3. Assign Function Modules to Logical Messages and Idoc types:- Transaction WE57
    4. Create process codes : Transaction WE42, and link the z-function module.
    5. Create partner profile: transaction WE20 and attach the message type and process code.
    6. In the Z- function module, extract data from the idoc segments, do whatever processing you want to do, and then call BAPI_CREATE_SALES_ORDER_FROMDAT2.
    Try the Trasaction WE19 for testing your inbound and outbound IDOCs
    Good Luck and Reward me for the same
    Thanks
    Ashok.N

  • Need help for IDOC inbound function module !

    Hi guys please help me to create a IDOC inbound function module.
    What are the parameters and tables.
    How to write the code.
    What it does.
    Please send me one inbound func module code if possuble
                                                                                  Thanks

    Hi,
    You need to create an inbound function module. Then define the process code in transaction we42 and attach the function module to this process code.
    In the function module you create you need to define tables of types EDIDC (Control record (IDoc)), EDIDD (Data record (IDoc)) and BDIDOCSTAT (ALE IDoc status (subset of all IDoc status fields)).
    Regards,
    Soumya.

  • LSMW idoc Inbound Processing settings

    Hi,
    We have done LSMW with BAPI method to create Bank master.
    In Idoc Inbound Processing settings -
    We created partner type as 'B' i.e, for BANK
    While creating Partner Number it is not allowing to create Partner Number. The error is  "Enter a permissible partner number"
    Please let me know what would be the problem.
    Regards,
    Hari
    Edited by: Bhatlapenumarthy Hari Krishna on Sep 12, 2008 9:31 AM

    Hi,
    Use patner type as US only and LSMW as Patner number.
    this will surely solve your problem .
    plz do this way :
    The first requirement is a file port for the file transfer. If required, create a port of the file type via Maintain ports. To do this, position the cursor on "File" and press Create. You should be in change mode. SAP recommends:
    Port: LSMW
    Name: Legacy System Migration Workbench
    Version: 3 (IDoc record types SAP Release 4.x)
    Outbound file Please enter a (dummy) physical directory and a file name, i.e. u2018filelsmwu2019 ·
    As an addition, you can specify a tRFC port. This port is required, if you do not want to create a file during data conversion but submit the data in packages directly to function module IDoc_Inbound_Asynchronous.
    SAP recommends:
    Port: assigned by the system
    Version: 3 (IDoc record types SAP Release 4.x)
    RFC destination: Name of R/3 System
    Name of port: Legacy System Migration Workbench.
    Then the partner type should be defined or selected. SAP recommends:
    Partner type: "US" (User)
    As of release 4.5A, this partner type is available in the standard system. Up to release 4.0B inclusive, this partner type is not available in the standard program and should be added. SAP recommends:
    Partner type: Create US
    Report name: /SAPDMC/SAP_LSMW_PARTNERTYPES
    Form routine: READ_USER
    Short description: any.
    Finally a partner number should be defined or selected. SAP recommends:
    Partner number: LSMW
    Partner type: US
    Partner status: A (active)
    Type: US
    Language: DE or EN
    Person in charge: Your user ID.
    Activate IDoc inbound processing
    reference : help.sap
    thanx.
    Edited by: Dhanashri Pawar on Sep 12, 2008 7:10 AM

  • 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

  • Idoc at status 51, however outbound delivery created

    Hi Gurus,
    We have peculiar issue , where in outbound delivery is getting created through IDoc. The inbound idoc has status 51 however delivery got created.  Any idea how is it possible?.
    Thanks in advance.

    Dear Math,
    Have you got the solution for the above. If you get can you tell me please because even i got the same error message while processing the IDOC
    status 51 after status 53. Outbound delivery is updated but not the sales order.
    can you please help me

  • Report RBDAPP01 not processing IDocs in status 51

    Hello guys,
    I have a problem with the execution of some Inbound Idocs using program RBDAPP01.
    Now the Idoc is executed in background with a job. Sometimes we have some locks because we receive idocs going to the same order, and then remain in status 51.
    In the variant of the job we filled to execute Idocs with status 64 and 51, but the idocs that remain in status 51 are not processed, at the end we have to do it manually.
    There is no parallel processo to avoid the locks.
    Do you know how we can solve it?
    Many thans in advance.
    Regards,
    Xavi.

    i do have the same problem. is there an solution to this?

  • IDOCs in status 64.

    For the message id COND_A near about 300 idocs are in there in staus 64.
    IDoc number            114390159
    Direction              2         Inbound
    Status                 64        IDoc ready to be transferred to application
      Port             SAPPR3
      Partn.type       LS         Logical system
      Function
      Partner number   ZLS_IM01   ZLS_IM01
      Port             NGACME
      Partn.type       LS         Logical system
      Partn.function
      Partner number   ZLS_IM01   ZLS_IM01
    please help us in this matter.
    Please ask me  if any further info is required.

    hi,
    You can use the program RBDAPP01 to post the idocs.. Please see in the partner profiles if you have specified either "Trigger immediately" or 'Trigger by Background Program".... if you have selected trigger by background program then basically idocs will be collected in bunch and then the program "RBDAPP01" is scheduled in background to process the idocs.
    Regards,
    Nagaraj

Maybe you are looking for