BBPIV IDoc Error Processing

Invoices are posted from SRM to ECC as IDocs whose message type is BBPIV. When there is an error in the IDoc input such as invalid IO and GL, invalid company code etc., these IDocs will be moved to status 51.
When IDoc is moved to status 51, work item need to be sent to approvers saying this IDoc has an error and need to be corrected. For this a workflow task needs to be developed.
In our system, there are two types of IDoc invoices sent to ECC. One is of type INVOIC01 and another is of type BBPIV01. There already exists a standard task TS00008057 which is activated for the event INPUTERROROCCURREDMM for IDOCINVOIC object type.
I shouldn't use the same event (INPUTERROROCCURREDMM) and IDoc object type(IDOCINVOIC) for BBPIV01, because responsible agents for both type of invoices are different in our company.
Please help us in getting this resolved. Also let me know if my approach is wrong towards this problem.
Thanks,
Rajesh

Use Transaction WE42 to identify the process code that is linked to your idoc type.
After you identify the process code, go to the detail screen and next to the "Identification" field you will see a button (ALE table). Click this button and it will take you to another detailed screen.
I assume that your Idoc Processing Type is via Function Module.
There will be a separate tab or block called "IDoc"
Choose the correct Object Type and in the fields Start event and end event configure the following values
INPUTERROROCCURRED INPUTFINISHED respectively.
You also need to create a agent (intended users to receive the errored Idocs via SAP Inbox) and map this info back in WE20 transaction.

Similar Messages

IDoc Error Processing workflow

Invoices are posted from SRM to ECC as IDocs whose message type is BBPIV. When there is an error in the IDoc input such as invalid IO and GL, invalid company code etc., these IDocs will be moved to status 51.
When IDoc is moved to status 51, work item need to be sent to approvers saying this IDoc has an error and need to be corrected. For this a workflow task needs to be developed.
In our system, there are two types of IDoc invoices sent to ECC. One is of type INVOIC01 and another is of type BBPIV01. There already exists a standard task TS00008057 which is activated for the event INPUTERROROCCURREDMM for IDOCINVOIC object type.
I shouldn't use the same event (INPUTERROROCCURREDMM) and IDoc object type(IDOCINVOIC) for BBPIV01, because responsible agents for both type of invoices are different in our company.
Please help us in getting this resolved. Also let me know if my approach is wrong towards this problem.
Thanks,
Rajesh

Hi Rajesh,
Using the same BOR object and event for two different idoc types is not necessarily wrong. There are ways to differentiate the responsible agents based on the idoc type if needed.
Here is how I would solve this:
Prerequisite: you need to make sure that event IDOCINVOIC.INPUTERROROCCURREDMM is triggered when your BBPIV01 iDoc is in error. To check that, you can activate the event trace and test your idoc (activate with tx SWELS, display with tx SWEL).
If the event does not trigger then you need to find out which event is getting triggered (using the event trace as well).
Now the serious business:
1. Create a copy of standard task TS00008057 that will be used for when BBPIV01 iDocs are in error.
2. Link this task to your event IDOCINVOIC.INPUTERROROCCURREDMM in transaction SWETYPV
3. Check in SWO1 if you have an attribute that gives the idoc type (or anything else which you can use to determine wich workflow should start in each case).
If not you need to create a subtype of IDOCINVOIC and in the subtype create an attribute that returns the iDoc type. Then you would need to delegate IDOCINVOIC to your subtype.
4. Create start conditions (tx SWB_COND) in which you check that TS00008057 starts only when idoctype is INVOIC01 and your new task starts only when idoc type is BBPIV01.
Cheers,
Patrick

IDOC error processing using WORKFLOW

Hi ,
I tried to post an error IDOC of message type FIDCC2 using "INPUTFORGROUND" method of Idoc object IDOCFIDCC2.I am using foreground from error for processing the idoc from the error status screen. For some Idoc it is going to the application and I can correct data and for some Idoc it just creates a message "Error during application input" . It is not calling the application dialog . Does anyone have answer for this? ,It would be a great help.
Thanks

Hi Siridhar,
Thanks for your reply . The message says application error ie it is calling application and trying to post.
For some error this calls the application in foreground and processing. Is there processing status of IDOC that it will not allow to process foreground.
Regards
Radha

Error : Pre Settings for IDoc inbound processing are missing error

Hi Experts,
There is a CRM job which executes LSMW and I am facing a strange problem during the IDOC posting the error "Pre Settings for IDoc inbound processing are missing error". Can anyone please tell me how to correct this error?
Thanks in advance.
Madhurima.

I'd start with the following document, with one modification. At step 12 after typing GEARAspiWDM press the Enter/Return key once prior to clicking OK. (Pressing Return adds a carriage return in the field and is important.)
[iTunes for Windows: "Registry settings" warning when opening iTunes|http://support.apple.com/kb/TS3299]

IDOC Error V1 042 - Sales document X is currently being processed by user X

Hello Experts,
I am using the IS-Retail solution of SAP and I am facing a IDOC Error which keeps the IDOC in Status 51. I traced the Error Message and it was V1 042. I am using an Inbound IDOC 'SHP_OBDLV_CREATE_STO01' to create the STOs (Deliveries) using the POs and there is a locking issue of the PO giving error message 'Sales document XXX is currently being processed by user XXX'.
I have created a backgroung job using a program to post the STOs using IDOCs that picks up multiple files from Application Server and processes them one by one. Now when 2 or more files use the same PO then this error occus.
I added a couple of minutes of wait time between the file processing but that did not help.
Please let me know if you have faces same situation and what solution did you apply.
Regards,
PS

Hopefully you have fixed this by now, but for anyone else who might be looking at this problem. We had this problem and we had the 2 programs check to see if the other was already runing. If so the program would submit itself for a number of minutes, different for both programs, and then exit. We also, and just before this, checked to make sure that there were not 2 of the running programs running and if so to exit. This was necessary because re-scheduling could put a program in conflict with itself. I hope that this may help someone. We used the join V_OP and searched for the program name, not the job name.
Kevin

AES filing error - Idoc Outbound Processing: EDI number cannot be compiled

Hi Gurus,
We are configuring the AES filing.
we've done the EDI configI and initally we got the error that EDI partner is not maintained. As per the suggestions from this Forum we've added the cusoms office details in geography tab.
Now when we are trying to process the same, we are getting the error "Idoc Outbound Processing: EDI number cannot be compiled"
All suggestions are welcome.........
Thanks in Advance.

Hi Shiva,
Here goes the solution: you need to maintain the Number of the Number Ranges starting with "10" and this applies only to GTS system as this is HARD-CODED in the Program, apart from 10 any number of the number range will result in an "EDI Number Range compilation" error.
Cheers
Harsha

IDOC error message

hi gurus
in my client place, when ever system sees 3 error messages(canceled PO, canceled line item in PO, free goods) it will automatically reject them, now my requirement is to add new error meesages to this automatic rejection program.
so please suggest me what would be the possible solution for this kind of issue.
thanks in advance
bob

Hi,
If u r using the Z Message type & Z funtion Function Module , these are the following steps to be checked...
Process Code : WE42.
Function Module : SE37
Message : WE81
Assign message : WE82
Assgin FM : we57
Characterstics OF FM : BD51
please check if ure function module interface is as per the template below:
IMPORTING
INPUT_METHOD LIKE BDWFAP_PAR-INPUTMETHD
MASS_PROCESSING LIKE BDWFAP_PAR-MASS_PROC
EXPORTING
WORKFLOW_RESULT LIKE BDWFAP_PAR-RESULT
APPLICATION_VARIABLE LIKE BDWFAP_PAR-APPL_VAR
IN_UPDATE_TASK LIKE BDWFAP_PAR-UPDATETASK
CALL_TRANSACTION_DONE LIKE BDWFAP_PAR-CALLTRANS
TABLES
IDOC_CONTRL STRUCTURE EDIDC
IDOC_DATA STRUCTURE EDIDD
IDOC_STATUS STRUCTURE BDIDOCSTAT
RETURN_VARIABLES STRUCTURE BDWFRETVAR
SERIALIZATION_INFO STRUCTURE BDI_SER
This is the general required format for IDoc inblund processing using FM.
Reward Points if it is Useful.
Thanks,
Manjunath MS

Outbound IDOC( Error passing data to port)

Hi,
We have an interface running daily configured such that the idocs are converted to files and placed on a directory path.
All the idocs are processed successfully but for one hour the idocs failed and the error message says:
Status: Error passing data to port
Error at OPEN (Directory path) with operating system error msg.:No such file or directory.
The missed data from the error idocs have been sent via PFAL.
But again after this one hour the idocs were successfully posted for the same directory path.
Please let me know what the issue can be here or how can we avoid this.
Thanks.

Hi
*Some times it may happen that IDOC doesnt reach to the port , in case if you are using Transactional RFC port so*
*you can use the report RSEOUT00 for sending the IDOC to port .*
*Hope it may help you .*

IDoc Errors in ECC

Hi Experts,
what kind of IDoc Errors can occur in ECC for the scenario :
ECC sending PO to Ariba(E-commerce hub, using third party adapter) and in receiving back Order confirmation from it.
Thank you,
MK

Hi,
This depends on the design and landscape and also Disaster Recovery or High Availability Plan.
some hints:
1. Connection Problem: Because of timeout , unavailability of the Receiver system.
2. Data Problem may cause you the error in IDoC posting [ probably functional/Business Team should look into this]
3. User ID and Password Maintenance - it may hit sometimes
4. If any pre-requisite process is required to process this IDoC, then problem in the pre-requisite process will lead the problem
these all kind of problems you may face..
Rgds , Moorthy

INVOICE EDI Inbound IDOC error

Hi,
We have implemented Support pack SAP_APPL SAPKH47027. And now we get
the Following error in IDOC inbound processing message type INVOIC during intercompany billing to post vendor invoices.
Error message: 'Field BSEG-BSCHL (1) (is not an input field)'.
I find that this is due to the OSS note: 960639 that has come along
with this Support pack.
Also SAP has mentioned a corection note to this problem. OSS note:
1032469.
But this Note 1032469 is not clear.
It is mentioned that..
"You explicitly enter the tax amounts in the IDoc
You can enter the tax information either at item level in
segment E1EDP04 or in header segment E1EDK04."
Is SAP suggesting to enter the TAx amounts (E1EDP04-MWSBT)?
And shud the coding be done during the Inbound processing function
module:
IDOC_INPUT_INVOIC_FI or during the outbound processing RSNASTED
(EDI_PROCESSING). We use SAP standard functionality.
Can anybody please explain what SAP has suggested to do techincally.
Regards,
Midhun.

Hi,
I checked both OSS note 960639 & 1032469. I neither find anything in first note ( 960639 ) which could cause this probem nor in the second note ( 1032469 ) which solve this problem. The only way to check is by doing what note 1032469 is saying.
One more thing you can do is debug the code, put the break-pointe message statement and findout where this error message is coming. Then you can check the code to find out the reason for this.
Can you also check if you are getting the same message when you try to enter same data directly in SAP using FB01 or whatever the relavent transaction is.
Regards,
RS

JDBC receiver adapter - Error processing request in sax parser

Hello,
I want to INSERT idoc data via JDBC adapter into a MS SQL database. After digging through SAP Help, numerous blogs and forum discussions on SDN and even posting an OSS message I still get the same error:
'Error: TransformException error in xml processor class: Error processing request in sax parser: No 'action' attribute found in XML document (attribute "action" missing or wrong XML structure)'
When testing my mapping in the Integration Repository the resulting XML message is:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:Employee xmlns:ns0="http://prodrive.nl/xi/HRMasterdata/HRMD_A_2_d_bcommerp">
 <STATEMENT>
 <T_PD_Employees action="INSERT">
 <access>
 <KeyTag>00088888</KeyTag>
 <PerNo>00088888</PerNo>
 </access>
 </T_PD_Employees>
 </STATEMENT>
</ns0:Employee>
The connection to the database is fine, Sender adapter with a SELECT * works perfect.
Can anyone help me solve this problem? I'm lost.
Best regards,
Roelof Jan Bouwknegt

Hi Bhavesh,
I have tried out the change you suggested. Without success. Message I get back is
- 2006-12-28 10:34:08 CET: Error: TransformException error in xml processor class: Error processing request in sax parser: No 'action' attribute found in XML document (attribute "action" missing or wrong XML structure)
structure in testtool:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:Employee xmlns:ns0="http://prodrive.nl/xi/HRMasterdata/HRMD_A_2_d_bcommerp">
 <STATEMENT>
 <T_PD_Employees action="INSERT">
 <ACCESS>
 <KEYTAG>00088888</KEYTAG>
 <PERNO>00088888</PERNO>
 </ACCESS>
 </T_PD_Employees>
 </STATEMENT>
</ns0:Employee>
Somehow the SAX parser doesn't like the result of my mapping. Maybe there is something wrong with the structure cardinality. Let me describe what I have built:
XSD:
WA_T_PD_Employees - Complex Type
> STATEMENT - Element - Occurence = 1
>> T_PD_Employees - Element - Occurence = 1
>>> STATEMENT - Attribute - Occurence = optional
>>> access - Element - Occurence = 1..Unbounded
Best regards Roelof Jan and thanks for your quick response

Error processing request in sax parser

Hi all,
I am doing an asynchronous interface.
It is an interface from IDOC to JDBC. While testing the interface,am getting the following error
"Error processing request in sax parser: Error when executing statement for table/stored proc. 'put_delivery' (structure 'Statement_Delivery'): java.lang.NumberFormatException: null"
Any kind of help is appreciated.
Regards,
Thireesha.

Hello,
Please refer to SAP NOTE 801367.
In advanced tab, use logSQLQuery-->true. Tt will display the actual sql statement in audit log instead of xml format.
You can copy this sql statement and execute directly in database to check the problem.
-Rahul

FlatFile 2 IDOC: Error in Communication Channel Monitoring

The given below is the Audit Log:
===========================
Error convert()
Error: convertCalledFromModule()
Error: process()
Error process()
Error MP: Exception caught with cause javax.resource.ResourceException: --- Conversion of synchronous request from module chain ended with errors ---[Error:ID=3069;LEVEL=3] SegmentDescription: checkAndResetChildrenCounter() not enough repetitions of the segment S_BGM found: 0 instead of 1 offset :2588 DESCRIPTION: SegmentDescription Warning: Not enough repetitions of the segment S_BGM ([not specified]/[not specified]).
Note:
My IDOC has S_BGM with 1..1 occurance.
S_BGM is created at the target.
But still, the above excception.
Can any one provide the solution?

Hi,
The test is successfull in the IR.
Error shown in communication channel moni.
I hope, mapping a constant is not required here as S_BGM is a 1..1 (occurance)
Edited by: santosh kumar on Dec 19, 2007 12:53 PM

Alert with IDOC error message

Hi All
We are configuring IDOC monitoring process in BPIM of Solution Manager. One of our requirement is Alert mail should include IDOC number and error message.
Example
IDOC Number: 8358000
Status: 51
Message: Payment term not found
Could you please tell how to configure error message in alert?
Regards
Raju

Dear Raju,
Idoc monitoring functions and capabilities are explained in following documentations:
www.service.sap.com/bpm -> Media Library -> Technical Information-> Setup Guide - Interface Monitoring
"Business Process Monitoring functionalities in SAP Solution Manager u2013 ALE / IDoc Monitoring"
/people/johannes.fleig/blog/2008/05/25/new-business-process-monitoring-functionalities-in-sap-solution-manager-150-ale-idoc-monitoring
As you can read in the above documentations, the alerts display the total and delta number of IDOCs found.
In order to get the detailed error message for an alerted IDOC, you must click on the "Detail Info" button, to access the monitored system and read the buffered information for the alert.
Thefore, it is not possible to get this information in the alert email as this text is not displayed per default.
An idea to overcome this would be, that you setup IDOC monitoring for the different message types (i.e. MATMAS), and then
specified further on key figure level using the parameters "Status Message ID" and "Status Message Number", and entering the Message Text as Alert Name (column "short text" ). This way you would get the message text in the email.
Please see the example in the above SDN Blog, screenshots 2 and 3.
Maybe you could also check if, changing the email configuration via the BADI, you cold add the required informaitons to the mails. To get details on this please see another useful SDN blog:
"Create your own auto-reaction messages in Business Process Monitoring via BAdI exit"
/people/johannes.fleig/blog/2010/06/02/create-your-own-auto-reaction-messages-in-business-process-monitoring-via-badi-exit
A complete description on how to set up auto-reaction messages in BPMon, and to implement and work with BAdIs in the BPMon environment, can be found in the u201CSetup Guide u2013 Auto-Reaction Messagesu201D which is available on SAP Service Marketplace, alias BPM (http://www.service.sap.com/bpm -> Media Library -> Technical Information).
I hope this helps,
kind reagrds,
Marta
SolMan Team

Idoc error message "This change has been superseded by another"

Hi,
I am trying to process multiple idocs together which will create/update info records using the program RBDAPP01. But it is processing correctly only single record and for all other records its giving the error message "This change has been superseded by another"
The function module used for processing is IDOC_INPUT_INFREC and when I checked this error is coming from it. Infact it is comparing the output of FM IDOC_SERIALIZATION_CHECK and populating the error message.
If we process the same record in single, it is processing correctly and not giving such kind of message.
I am not sure what is happening here. Please help.

I was trying to create multiple PIR for same material using multiple idocs. And that is the reason it is giving the error when trying to process the idocs together. When I tried changing the same into one record ie different PIR for same article in one idoc, its processing correctly.

BBPIV IDoc Error Processing

Similar Messages

Maybe you are looking for