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

Similar Messages

Changing Rejected Sales Order Items with BAPI?

Hi Forum,
I have the following challenge, would be great if someone of you could help me out. Will help me solve some of my performance problems.
I have sales orders which are temporary and have 'rejected order items'. Now the requirement is that I have to change the 'rejected order items' (quantity and Delivery dates) based on some XYZ criteria. Now using the BAPI_SALESORDER_CHANGE bapi I have to
1. first get rid of the 'REJECTION REASON'
2. Change the order item and then reset the above.
I tried doing it by populating the order_items internal table with two entries but to my surprise it works once and fails twice!!! I get some errors that are totally irrelated and wierd.
As for now, I've just adjusted the program(dirtily??) and will be calling the BAPI twice for a change !!!(Huh!)
Now if anybody knows how to deal with the above problem just drop a few lines, will be of good help to me.
Thanks and regards,
ZAM

Hi Srinivas,
Thanks for the reply. The rejection reason is set manually, when creating the sales order. I do set the update flag to 'U' and also activating all the X structures. But still it did not work.
Let me put it very simple. Is it possible to change the rejected order items, through BAPI's? If yes, how?
Regarding the error messages I will have to change the code again to recreate the messages will let you know as soon as I am finished with some things. But however here are some errors
Field 'WMENG' cannot be changed, VBEPKOM 000100 0001 ready for input
Field 'WMENG' cannot be changed, VBEPKOM 000100 0001 ready for input
Sales document 0030000031 was not changed
there are few others which appear now and then indicating a system error !!
thanks,
ZAM

Mass change with Reason for Rejection.

Dear Gurus,
Pl tell me the process to close all the open orders at one go. I have tried with the t.code MASS, but I was unable to do that.
Pl give the step by step process.
Regds,
Sreehari

Hari,
MASS transaction is useful, If you know what fields to change and in what documents/customers/vendors/.
In your case what fields is pretty clear (VBAP-ABGRU or MASSVBAP-ABGRU )
But what documents is not clear.
Points to consider.
     You can the documents that are open by just writing some query or even you can get it from SE16 using VBAP table
        and you can use these document numbers and enter in the MASS T.Code.
It looks simple but the main hurdle is not all of the items in these orders are open, right...so you can't enter the reason for rejection in an item which was already delivered, or scheduled to deliver.
So Unless you know that all the items of an order are open, its not feasible to use MASS T.code.
         So my suggestion is to write an ABAP program that check whether the item in an order is open or not and then change the reason for rejection using BDC code.
                Thats my suggestion. I hope you understood the reason for going to an ABAP program.
Regards,
Ajai.
Reward points if helpful.

Tcode to view the list of orders with reason for rejection

Hi friends,
Can any one tell the T.code or report to view the list of sales orders or Scheduling agreements with Reason for Rejection updated.
Kindly help.
Regards,
K.Vivek

Hi Vivek,
Use Tcode VA05 i.e. List of Sales Order. In this Tcode you can enter sales document type, sales area and other related data. After execution, from layout you can select Reason for Rejection from the list.
This way you can filter all the sales documents including Scheduling agreements by using sales document types.
Hope this will help you.
regards,
Sagar Wagh

Mapping from File to IDoc with multiple Idocs and multiple line items?

Hi All,
Need some help with mapping, requirement as below: I have a flat file with multiple records, need to create multiple idocs per each separate order in flat file with as many line items.
Order_1 field-1 field-2 field-3 field-4
Order_1 field-1 field-2 field-3 field-4
Order_2 field-1 field-2 field-3 field-4
Order_2 field-1 field-2 field-3 field-4
Order_3 field-1 field-2 field-3 field-4
Order_3 field-1 field-2 field-3 field-4
I have imported IDoc changed to 1:Unbounded, able to create multiple Idocs based on separate order from flat file.
Order_No - removeContexts - splitByValue(ValueChanged) - collapseContexts - exists - creatIf - IDOC
Now I am having hard time creating a line item segment E1EDP01. I want to have Idoc created below way:
IDoc-1 (Order_1)
E1EDP01
E1EDP01
IDoc-2 (Order_2)
E1EDP01
E1EDP01
IDoc-3 (Order_3)
E1EDP01
E1EDP01
I am getting multiple IDocs created. Please help me to create mutlieple line items under each Idoc. Please be speficic about the node funtions to be used, because I tried many times with different combinations, didn't work.
Regards,
N@v!n

Hi Navin,
Create your source structure like below
<Order>1 to unbounded
    <Order_No>
    <field1>
    <field2>
    <field3>
    <field4>
</oder>
to create mutiple IDocs based on order number,use below logic
Order_No-->removecontexts--->sort--->splitbyvalue(Valuechange)--->collapsecontext-->Idoc
use below logic for E1EDPO1,
Order----->removecontexts------>
                                                                                formatByexample------>E1EDP01
Order_No-->removecontexts--->sort--->splitbyvalue(Valuechange)-------->
try above logic and let me know if you any issues.
Regards,
Raj

Reason for rejection for completed item

Hi All,
How to give reajon for rejection for a completed item?
Because after delivery of an line item the reason for rejection field is coming in grey mode.
So how to make it in change mode so that i can put reasonf for rejcetion.
Waiting for valuable advise.
Regards
Ashis

Hi Ashis,
Why you want to set the reason for rejection for already rejected item. Is the Document still in Being processed sate even after billing and delivery? If it is then check the completion rule in the Item category deinition. If the Table has not got update then you can run the report "SDVBUK00" to make the document complete. Please not that this works only if the status in the data base is complete. Other wise If you want to set the reason for rejection for the items that have the completed status , you have to cancel the Inovice and reverse the goods Inssue(VL09) and then set the reason for rejection. Kindly please let me know If you need any more information on this.
Regards
Ram Pedarla

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 !!!

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

Change the sales order reason for rejection for line item

Hi,
i want to change the sales order reason for rejection for line item.
iam using bapi_salesorder_change.but i unable to change the sales order.
if possible please provide me what are the fields necessary for changing
sales order reason for rejection for line item.
Regards,
Suresh

This is the standard config to supress printing on the rejected item. Are you using standard programs or customised ?

SQL30082N Security processing failed with reason "15" (PROCESSING FAILURE)

Hi all.
I'm managing the following error during a system copy:
<b>SQL30082N Security processing failed with reason "15" ("PROCESSING FAILURE").
SQLSTATE=08001</b>
Inside the db2diag.log, i have the following message:
<b>2007-10-15-16.44.56.793439+120 I718413554A270     LEVEL: Warning
PID     : 483450               TID : 1
FUNCTION: DB2 Common, Security, Users and Groups, secLogMessage, probe:20
DATA #1 : String, 64 bytes
Password validation for user sapr3 failed with rc = -2146500315</b>
Can anyone help?
Thanks and regards,
Marco.

Hi,
check if the files
$INSTHOME/sqllib/security/db2c?pw
have the correct permissions. They need a SUID bit to root.
If the SUID bit is not set, you can do a
<db2_install_dir>/instance/db2iupdt db2<dbname>
as user root to update your DB2 instance. This will set the permissions correctly.
Regards
               Frank

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

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)

Open status of Credit Memo after rejecting all line items

Dear Gurus
I am facing a problem. In my company we are using 2 credit memo types. One is CR and other ZCR (Copy of CR). I have tried both but both have same problem. I have also tried creating credit memos with reference to billing document, sales document and without reference also but the issue is same.
Problem is this we create credit memo with VA01 and post it with VF01. After posting if we cancel its posting with VF11 and reject the line items in VA02 the status of credit memo remain open. Cancellation documents are ok and completed but only credit memo in VA02 remain open even after rejecting all line items.
I have checked incomplete log of sales document type (CR and ZCR) in VOV8 and item types (G2N) in VOV7. All fields which are defined in incompletion log are there in document header and item.
Following is the copy paste data of Header Status tab
Overall status       Open
Rejection status     Everything rejected
Credit status        Not performed
Bill.stat.order-rel. Not invoiced
Overall blkd status Not blocked
Header data     Complete                   Item data       All items complete
Header dlv.data Complete                 Item deliv.data All items complete
Header bill.dat Complete                   Item bill.data All items complete
please help.

dear sir
if you mean to say to check Reason for rejection's settings in OVAG i have checked it and all rejection reasons are being in use in all other sales documents too. They are working fine in all other sales document. Issue is only in these two credit memos types.
Assigned by the System (Internal)
Delivery date too late
Poor quality
Too expensive
Competitor better
Guarantee
Unreasonable request
Cust.to receive replacement
Transaction is being checked
These are reasons and Stat column is empty for all. Other 3 columns have no tick in any reason.

REJECTION OF LINE ITEMS IN SALES ORDER ??

Friends !!
1)If there are 10 line items in a sales order two line items should be rejected and the same rejected items should not be displayed in an invoice output? Where will it be configured in IMG. (The items should not be deleted from VA02 it should be is sales order)
2)tell me the process of creating requests in SE10, as there are different module people are working how do they know which request they have created at time of releasing,i have needed detail process step by step.
kindly sent me details plz.
Yours,
Sreedhar

HI
Rejecting Items in a Sales Order
You can enter a reason for rejection for one or more items. These items are then not copied into the subsequent documents. If you reject an item in a sales document, the system automatically cancels any materials planning requirements (MRP) previously generated for the item.
Prerequisites
You must be in the change mode for a sales document.
Procedure
You can either reject the whole sales document or individual items.
Reject all items:
If you want to reject all the items, choose Reject document in the change modus for the sales document.
The system automatically selects all the items and you can enter a reason for rejection in the following dialog box.
Enter the appropriate reason for rejection and choose Copy.
The system assigns the same reason for rejection to all the selected items.
Reject individual items:
If you only want to reject some of the items, select those items in the item overview screen and choose Edit ® Fast change of... ® Reason for rejection.
A dialog box appears in which you can enter the appropriate reason for rejection.
Enter the appropriate reason for rejection and choose Copy.
The system assigns the same reason for rejection to all the selected items.
Reject individual items with different reasons of rejection:
If you want to enter different reasons for rejection for the items, choose the Reason for rejection tab page from the overview screen when changing the sales document. You can enter a different reason for rejection for each item in the Reason for rejection field.
2)You can distingiush the transports depending on the
component and the package for sales and the application it will be sales
Sail

Generate 2 line items with posting keys in same table while using FM .

Dear Expert ,
For T-code f-65 ,I have to park a FI Document .i tried with PRELIMINARY_POSTING_FB01 for parked Document . But i am not successfully park the document .
with the help of F-65 the data Segregate between Tables VBSEGS and VBSEGD with respecting Posting key . but with this Fm entire entry is displaying in table VBSEGS .For example it generated two line items with posting keys '15' and '40' and these both are displayed in VBSEGS whereas posting key '15' has to be displayed in VBSEGD.
when i check this Document in FBV0 Error reflect " G/L Account 0012000 1001 Does not Exist ".
Here my code -
DATA:   XT_BKPF LIKE BKPF OCCURS 0 WITH HEADER LINE ,
        XT_BSEG LIKE BSEG OCCURS 0 WITH HEADER LINE ,
        XT_BSEG1 LIKE BSEG OCCURS 0 WITH HEADER LINE ,
        XT_BSEC LIKE BSEC OCCURS 0 WITH HEADER LINE ,
        XT_BSET LIKE BSET OCCURS 0 WITH HEADER LINE ,
        XT_BSEZ LIKE BSEZ OCCURS 0 WITH HEADER LINE ,
        XT_BKORM LIKE BKORM OCCURS 0 WITH HEADER LINE ,
        XT_THEAD LIKE THEAD OCCURS 0 WITH HEADER LINE ,
        XT_SPLTTAB LIKE ACSPLT OCCURS 0 WITH HEADER LINE ,
        XT_SPLTWT LIKE WITH_ITEMX OCCURS 0 WITH HEADER LINE .
DATA :    XTEXT_UPDATE LIKE BOOLE-BOOLE VALUE SPACE,
          XTEXT_ITEM_UPDATE LIKE BOOLE-BOOLE VALUE SPACE,
          XI_UF05A LIKE UF05A,
          XI_XCMPL TYPE XFELD VALUE 'X',
          XFS006_FB01 LIKE FS006 ,
          XI_TCODE LIKE T020-TCODE VALUE 'F-65',
          XI_PARGB LIKE RF05A-PARGB        ,
          XI_TCODE_INT TYPE TCODE           .
DATA P_RETURN LIKE BAPIRET2 OCCURS 0 WITH HEADER LINE.
XT_BKPF-BUKRS     =     'CP01'.
XT_BKPF-GJAHR     =     2011.
XT_BKPF-BLART     =     'DZ'.
XT_BKPF-BLDAT     =     SY-DATUM.
XT_BKPF-BUDAT     =     SY-DATUM.
XT_BKPF-MONAT     =     '06'.
XT_BKPF-CPUDT     =     SY-DATUM.
XT_BKPF-WWERT     = SY-DATUM.
XT_BKPF-USNAM     =     'ABAPER'.
XT_BKPF-TCODE     =     'F-65'.
APPEND XT_BKPF.
XT_BSEG-BUKRS     =     'CP01'.
XT_BSEG-GJAHR     =     '2011'.
XT_BSEG-BUZEI = '001'.
XT_BSEG-BSCHL = '40'.
XT_BSEG-KOART = 'S'.
XT_BSEG-SHKZG = 'S' .
XT_BSEG-GSBER     =     'CPLN'.
XT_BSEG-BUPLA = 'CP01'.
XT_BSEG-WRBTR     =     10000.
XT_BSEG-PSWSL = 'INR'.
XT_BSEG-ZUONR = 'CH. 123456'.
XT_BSEG-HKONT = '241000'.
APPEND XT_BSEG .
CLEAR XT_BSEG.
Vendor line item - required even for header only - BSEG table
XT_BSEG-BUKRS     =     'CP01'.
XT_BSEG-GJAHR     =     '2011'.
XT_BSEG-BUZEI = '002'.
XT_BSEG-BSCHL = '15'.
XT_BSEG-KOART = 'S'.
XT_BSEG-SHKZG = 'H' .
XT_BSEG-GSBER     =     'CPLN'.
XT_BSEG-BUPLA = 'CP01'.
XT_BSEG-WRBTR     =     10000.
XT_BSEG-PSWSL = 'INR'.
XT_BSEG-ZUONR = 'CH. 123456'.
XT_BSEG-HKONT = 'PC04000001'.
APPEND XT_BSEG .
CLEAR XT_BSEG.
CALL FUNCTION 'PRELIMINARY_POSTING_FB01'
   EXPORTING
     TEXT_UPDATE            = XTEXT_UPDATE
     TEXT_ITEM_UPDATE       = XTEXT_ITEM_UPDATE
I_UF05A                =
     I_XCMPL                = XI_XCMPL
FS006_FB01             =
      I_TCODE                = XI_TCODE
I_PARGB                =
I_TCODE_INT            =
IMPORTING
    XEPBBP                 = CHECK_A
    TABLES
      T_BKPF                 = XT_BKPF
      T_BSEG                 = XT_BSEG
      T_BSEC                 = XT_BSEC
      T_BSET                 = XT_BSET
      T_BSEZ                 = XT_BSEZ
T_BKORM                =
T_THEAD                =
T_SPLTTAB              =
T_SPLTWT               =
          EXCEPTIONS
            ERROR_MESSAGE = 1.
P_RETURN-ID         = SY-MSGID.
P_RETURN-TYPE       = SY-MSGTY.
P_RETURN-NUMBER     = SY-MSGNO.
APPEND P_RETURN.
     p_return-MESSAGE_V1 = XSYMSGV.
IF SY-SUBRC = 0.
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
      EXPORTING
        WAIT = 'X'.
ENDIF.
WRITE :/ sy-subrc , sy-MSGV1 .
Thanks ,
Ashish Gupta

Hi Raghuram,
I found a very important SAP Note 103051, details are below.
An IDoc processed by function module IDOC_INPUT_INVOIC_MM (of category INVOIC01) must not refer to the same purchase order item in several invoice items. This is also valid if for a goods receipt-related invoice verification several delivery notes belong to the same purchase order item.
Depending on the system settings and the situation, various error messages can occur (for example, FD240 'Order item ... selected more than once' or M8050 'Balance not zero: & debits: & credits: &').
In this situation module IDOC_INPUT_INVOIC_MRM generates error message M8321 'Document contains same order item more than once'.
For example, this situation occurs if you work with individual batch valuation and the SD billing document executes a batch split for different batches which belong to the same purchase order item and delivery.
Other terms
INVOIC, SAPLIEDI, M8047, M8, 321
Reason and Prerequisites
This is because of the program design.
Solution
There is no solution for IDOC_INPUT_INVOIC_MM.
Module IDOC_INPUT_INVOIC_MRM (only as of Release 4.0) for the logistics invoice verification can distinguish different goods receipts by means of the delivery note number. For this purpose, GR-related invoice verification must be active.
Owing to this symptom, billing documents for single batch valuation with batch split cannot be settled in MM-EDI inbound processing. The settlement generates exactly the situation described (several invoice items for the same purchase order item). In this case, the only solution is to deactivate the billing of the batch sub-items in SD Customizing and to calculate the main item only.
Hope this helps.
Reward if helpful.
Thanks

Rejection of PO item with reason 06 - IDoc failure

Similar Messages

Maybe you are looking for