Vendor IDOC failures

Hi Experts,
We have series of Vendors Masters updated through CREMAS IDOCs. But some of the CREMAS IDOCs fail as the BANK key in the Vendor is blocked by another user.
Actually the Mass vendor update happens as a result some of the bank keys will be locked up and a result IDOCs fail.
Can we have a solution for this scenario?
1. Vendor IDOC is updating a vendor master with a same bank key
2. another IDOC is updating another vendor master with a same bank key.
The second IDOC fails, can we avoid this ?
Please give a solution for the same.
Thanks,
Rohan

Hi,
I can suggest one solution, You can find a user-exit in inbound FM( you can find this FM in inbound process code).
Write a code in user-exit to check if the bank key is locked by other user by applying a lock and if it fails that's mean it is locked by other, put a wait time and try again.
Thanks,
Sajid

Similar Messages

How to send vendor IDOC data from SAP R/3 to XI.

Hi experts,
I have developed the IDOC to FILE scenario for Vendor Master Upload. I want to place flat file in local folder with in XI or Outside of XI. (Using NFS or FTP protocol in FILE adapter). My First quesstion is How to setup Folder with in XI ro Out side XI?
And also I want to push the IDOC from SAP r/3 to test the scenario. Both XI and R/3 systems are configured to exchange data.
How to Push Vendor IDOC from SAP R/3 to XI? (we can send XML directly to XI; but the R/3 kernal should be moe than 6.20).
Thanks in Advance.....

Hi,
>>My First quesstion is How to setup Folder with in XI ro Out side XI?
Its a normal way to creation of folders in Os level . u can create the folder in XI Server or on the FTP Server.
ALE Settings
Steps
SAP XI
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
In SLD System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system name.
IDoc-XI-File scenario
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
Posting the IDOC from R/3 to XI
/people/sameer.shadab/blog/2005/07/25/reposting-idocs-instead-of-recreating--for-testing-purpose-xi
REgards
Seshagiri

Park inbound EDI Invoices on iDoc failure from a workflow?

Hello all,
We have seen note 501524 that talks about parking inbound invoices by default.
Our situation is this. We are expanding our use of EDI for inbound invoices. As such we would like to automate the validations steps as much as possible. To date with our limited use we have set up a workflow to notify on idoc failures and then a few agents have access to BD87 to make the idoc right and reprocess. We don't want to continue this process.
Our preference would be to continue to allow the iDoc to fail, the workflow fires but at this point we communicate the failure to the appropriate person and park the invoice.
Does this sound like a reasonable approach?
Can we even park a red lighted iDoc?
Once parked can the invoice be dealt with without using BD87?
Has anyone ever tried this?
Thanks,
Doug

Hi Ralph,
In my opinion, you must have a PO Number for Invoice if you want to use standard functionality. You will probably need to create IDOC using an ABAP program which reads this file and search for PO based on the information available to you. I also notice that you are missing material number as well, how do you match the item number in the PO ?
I don't see a way aroung without writing an ABAP program to handle this logic, but you can still use IDOC ( which comes with the standard processing logic and that is a big advantage ) so that you need to write only the PO matching logic.
or if you are not inclined to write a separate program for uploading file into SAP and formatting IDOC, you can write your own process code (FM)for INVOICE01. Inside this process code (FM), you can put your PO matching logic and then call standard FM (process code). This is what I usually do.
Cheers,
Sanjeev
Cheers,
Sanjeev

Intercompany Deliveries were created with zero quantity, causing an idoc failure and the remaining delivery too

Intercompany Deliveries were created with zero quantity, causing an idoc failure and the remaining delivery too
a. User trying to create delivery but stock not available.
b. When stock is not there it should show an error message in SAP screen but its not - like stock not available etc
c. Fedex gets delivery notice for the delivery; if its more than zero it will create delivery otherwise less than zero it won’t accept.
d. But issue its creating even its less than zero
Is there anyone who can help me out...

When one is created with zero quantities it starts blocking our deliveries from getting through to fedex because deliveries will in doubt have been blocked at fedex. As we process our orders in morning and if there is an STO blocking orders, it will be in afternoon .
Any suggestions !!!

Rejection of PO item with reason 06 - IDoc failure

Hi,
There is an IDoc failure with message: Rejection of PO item with reason 06.
The user(supplier) wants to reject first line item of the Subcontracting PO and add a new line item instead with the right data.
Please suggest.
Regards,
Akash Prekar

Hi Dirk,
You can actually use the BADI BBP_CREATE_PO_BACK to change the flag value before filling the PO Craetion BAPI interface parameters
Sangeeta

Standard Vendor IDoc CREMDM04 needs to be triggered from the transactions

The Standard Vendor IDoc CREMDM04 needs to be triggered from the following transactions:
u2022XK01 (Create Vendor)
u2022XK02 (Modify Vendor)
u2022User Exit EXIT_SAPOTM_VEND01 .
The following are some more details:
u2022Receiving System: SAP PI
u2022Sending System: SAP ECC
u2022Direction: Outbound from SAP ECC.
How do we achieve it ??
BR.
Tan
Moderator message: please do more research before asking, show what you have done when posting.
Edited by: Thomas Zloch on Feb 20, 2012

Hi,
In Tx. WE42, Select the process code for the corresponding partner and bind your workflow / task inplace of the function module with the process code. Now, this will enable the idoc to get placed in the agents(identified by that workflow)inbox.
But to design the workflow, you`ll have to use tx. swdd and prior to that get some basic understanding of Business Workflow from SAP Library.
Hope the info. is helpful and reward points if so.
Regards

Vendor IDOCs are not uploading in LFA1 table

Hi All,
We have a SAP system where Vendor IDOCS are coming from MDM through SAP PI middleware. The problem we are facing is we are not able to see all Vendors in LFA1 table.
In WE05 IDOCS are posting successfully but when we check for respective vendors in LFA1 table only few vendors are available there.
Can anybody guide us to solve this issue? Also pls let us know the process of uploading master data into table as we are very new in ABAP.
Regards,
Sarita

be open minded. SAP gives several import methods to load vendors. one of them is per IDOC.
But the vendor master IDOC does not automatically create the adress master.
And even more important, if you migrate data from one SAP system to another, the IDOC method is more straight forward than the batch input, because you can send the IDOCs from legacy system to new system, you will then have a 1:1 relation of the structure in LSMW and you can create vendor masters by knowing the new vendor number from an internal number range already in LSMW, long before you actually post the vendor. With batch input you can either post with numbers from external number range, or you just dont know the new number already in LSMW.
And you dont need to download the data to Excel. And further, the LFA1 adress data has less information than the ADRC adress data.

RBDMANI2 Idoc Reprocessing IDOC Failure Notification

Hi SAP Friends,
I developed an inbound interface for LIV electronic invoice(MIRO) with basic type INVOIC02. At present everything going smooth.
i scheduled a background job with the program RBDMANI2 to reprocess the failed IDOCS. i.e if any failed idocs required SAP side changes, users will complete the changes. Then the scheduled job will process the failed IDOC.
IDOC will process if corrected data is satisfying else IDOC will fail again with Status 51.
Now the failed IDOC notification we are not getting any notfication.
If IDOC is failing first time idoc failure notification will come. At that point Object Type IDOCINVOIC & Event INPUTERROROCCURREDMM is triggering.
When i am reprocessing through the scheduled job of program RBDMANI2 , i am not getting any failed notification.
Can anyone help me out where i am missing the event. i need to activate any other event linkage for the reprocessing.
I tried with SWELS, i did not get any event when i execting the program RBDMANI2.
Appreciate your help and valuable inputs.
Thanks & Regards,
Srinivas Bhavanam

Srinivas, per my understanding the failure event is only triggered once. You can attest this yourself by executing the associated workflow. If you select the process option and all errors were not addressed, the current work item remains active ; eventually the error message will be changed in case the IDOC is now failing for another reason. There is only one workflow instance for the same IDOC ; the failed batch processing does not generate any new workflow or IDOCs, it only updates the current instances (workflow) and add an entry to the IDOC status table (EDIDS)

How to solve the INFREC Idoc failure with message type

Hi,
Please let me know how can we solve the INFREC Idoc with the message type" Not possible to set tax code without tax calculation schema"
Pl suggest me how to tackle this Idoc failure.
Regards
Raj

Hi,
An\ybody..please suggest.. It is very urgent..
Regards
Raj

IDOC FAILURE while sending data from ZEB_HCm systen to ZRA-EREC SYS

Hi
Experts
I am having idoc failure while sending data from HCM SYSTEM to EREC systems.
From that Data records i found the failure recored containing PERNR.
and from status record the
ERROE IS : No status information available for object CANDIDATE
Message no. HRRCF0001073
usually i used to run PFAL for these king of issues , when i tried to run PFAL for the PERNR it is giving the same errroe,
So pls suggest how to send the data to resiolve this .
Regards
Suresh

Hi Nitin,
The IDOC when came in Erec system is in error status ( 51).
When i saw the data records, only pernr were mentioned.
Then i send the idoc thru PFAL again by sending all information as O-C-S-P.
Still it is giving me the same error.

IDoc failure in background job

Hi,
I have developed a customized program and sending outbound IDocs to other SAP system using Function Module MASTER_IDOC_DISTRIBUTE. When I am running this program in background mode IDocs are failed with reason 'Entry in outbound table not found'.
But when I am running the same program in foreground then IDocs are getting posted properly. Partner Profile and port are set properly.
Please anyone could give me reason behind IDocs failure in background Job.
Many Thanks.

Hi,
Message Number for the message is "Entry in outbound table not found' E0 - 400. This Mesasge used
in the below programs.
Programs asying that there is no Entry in EDP13(Partner Profile : Outbound(Technical Parameters)) Table. Debugg the Background job in SM37 by entering JDBG in the command field then it will go to debugging mode. Then put break point for "MESSAGE".
Thanks,
Naresh Mochi

Inbound idoc failure(vendor invoice not posted)

Hi All,
we have two SAP systems. SAP A and SAP B.
SAP A is the vendor for SAP B system we have created a sales order/delivery/out bound invoice in SAP A system.The sales order has BOM material with main item and sub items. We have the same material master data and BOM master data in system A and system B since we are following split architecture.
The outbound invoice(with main and sub item) in system A has generated an outbound idoc and the idoc has gone to SAP
system B. There are the usual segments like E1EDP01 for main item and another E1EDp01 for the sub itmes in the outbound
idoc.The message type is INVOIC and basic type INVOIC02 with no extension.
In system B, the inbound idoc (coming from system A) has failed giving the error message "higher level items not allowed". The
segment E1EDP01 for sub item is highlighted in red ! basically the inbound idoc in sap system B is posting a vendor
invoice since the inbound idoc in B is calling the FM IDOC_INPUT_INVOIC_MRM... I think this is doing vendor invoice
verification.
I have checked in system A, all is ok and the outbound idoc is ok but the issue is in sap system B, the inbound idoc has failed
with message "higher level items not allowed". The segment E1EDP01 for sub item is highlighted in red in inbound idoc in
system B. The segments are the same for inbound idoc in B and outbound idoc in A.
Can someone pls tell what is wrong in system B.(config or data issue) as we are managing both systems.
regds

Hi,
I am not sure if we can send both main and sub items thorugh inbound invocie idoc to create vendor invoice.
you can try to post the idoc by removing main items from the IDoc in WE19.
one more thing you should aware is you are not allowed to to create two E1EDP01 segements for the same PO item(E1EDP02).
check this as well.
Regds,

DELVRY03 IDoc failure because of Locks

Hello All,
My Incoming Delivery confirmation (Delvry03) IDocs are failed due to "Delivery is currently being processed by another User "
I have cheked SM12 for this user , But couldn't find any locks for that user ...
Please share your Ideas to resolve this lock issues ...
Can you also let me know the best way to reprocess this failure IDocs for time Being...
am bit confused to choose the programs ( RBDAPP01, RBDMON00 or RBDMANI2 )
Best,
Lav.

HI Cherry,
At first look it looks to me a number range issue,please check in SPRO settings the number ranges defined for Vendor and customer,and confirm what MDM is sending.
Thanks,
Ravi

LSMW - Report to get IDOC failures and its external reference number

Hi All,
I'm currently using LSMW for data migration in CRM, for Business Partner and transaction data.
I need to generated a report which covers the idocs which have failed and the external identifier for which it has failed. Currently the IDOC reports that are available OOB provide the IDOC number and the reason for failure. It will be great if I can get the external identifier of the transaction as well.
I searched for a report in SAP but could not find any which gives this functionality.
Please advice.
Thanks in advance.

Hi,
1.)If you want the ouput in the same report program which triggers the idoc, it is better to use the control record information.
You will get IDoc Number from XEDIDC(check the below code) and you can store the idoc number into an internal table if more idoc is expecting to be triggered.
     call function 'MASTER_IDOC_DISTRIBUTE'
          exporting
            MASTER_IDOC_CONTROL        = EDIDC
          tables
            COMMUNICATION_IDOC_CONTROL = XEDIDC
            MASTER_IDOC_DATA           = XEDIDD
          exceptions
            others                     = 5.
   read table xedidc index 1.
append xedidc-docno to it_docno.
And finallly use this to display in the output.
2.) if u want it in a seperate report, then select based on date, idoctype, messagetype
Regards,
Sajith

Vendor idoc

I am using CREMS04 to try and create a vendor master record. However I am getting an erro saying invlaid function code. I am using the message code 009 to try and create the IDOC. Can anyone shed some light on how to create a simple vendor master record via an idoc.

I've taken out the 009 codes but still getting the same error. Any ideas?
I've ran the test idoc in the foreground and the underlying BDC performed by the Function Module gets stuck at the Purchasing data screen as its trying to enter the BDC code '=LTSU'. I'm not even putting any data in this screen but I have tried to add default data wiht no joy...
Message was edited by:
showthousand

Vendor IDOC failures

Similar Messages

Maybe you are looking for