Problem when setting Reason of Rejection for a sales order using IDOC

Hi All,
I am working on a requirement where i need to put a reason for rejection as 'Item Cancelled' for a sales order via IDOC 'IDOC_INPUT_ORDCHG' in a third party scenerio where the PR is created automatically from the sales order . When the IDOC is run in the foreground I get the information message Subsequent function " 'Purchase requisition from sales document' not possible Item & was rejected "(Message V1579) and the IDOC results in a error when run in the background mode because of the same information message. The message should not appear when a sales order is being processed in the background but still the message is being displayed . Is there any way the message can be suppressed ? Thanks in Advance.
Regards,
Sowmya.

can you send the program how you create a so or po using IDOC, as i've a assignment creating PO using IDOC & then creating a sales order of the PO. and i dont know how to create a IDOC. SO IF you have sample program it would be help full
Thanxs

Similar Messages

Unable to put Reason for Rejection for Return Sales Order

Hi
I am unable to put Reason for Rejection for Return Sales Order.
what may be the reason?
Reg,
Antaa21

hi
One of the possible reson could be, there is subsequent document created. Please check the VBFA table for document flow and see if there is any other document created for this line item, if yes then you have to reverse the same
Check whether this field is maintained as DISPLAY only or not
T-Code SE51(Screen Painter)
Give Program Name SAPMV45A
(before doing this confirm from the field from sales order, keep curcer on the pricing date press F1
and then select technical details)
Screen Number 4441
(before doing this confirm from the field from sales order, keep curcer on the pricing date press F1
and then select technical details)
Select Attributes radio button.
Go to Element list Tab. Inturn select Special Attribute tab in Subscreen.
For Field Name "VBAP-ABGRU" Check what is maintained might be it is maintained as DISPLAY only.

How to create an Invoice for the sales order using the T-Code VF01

Hello Experts,
How to create an Invoice for a sales order using the T-Code VF01?
Thanks in advace,
Suma

hi,
Make the following settings-
1. Create sales document and billing type
2. assign billing type in sales document type config VOV8
3. Activate itemcategory as sales order related billing
4. Maintain copy control header and item level between sales order and billing
5. Maintain pricing procedure for sales order and billing
6. Define Output procedure in case to print invoice
Regards
Goutham

Reason of rejection field in sales order

Hi All,
For a sales order when we create subsequent document i.e delivery...etc the reason for rejection field at item level gets Grayed out and the function module BAPI_SALESORDER_CHANGE is not updating it and returining the message " Field 'ABGRU' cannot be changed, VBAPKOM 000001 ready for input."
Is there any other function module or any other way to update the ABGRU i.e reason for rejection in sales order?
any help will be highly appreciated.:)
regards,
pavan.

Basically BAPI do the direct update to the tables, it will cross check with the configurations settings and not allowing to do the change for the particular field. Try to make it modifiable and run your BAPI it should work.

Problem creating sales order using IDoc ORDERS05 (Inbound)

Hello Experts,
We are trying to create a sales order using the IDoc ORDERS05 with process code ORDE for creating sales order. I am getting the following error "VKORG, VTWEG, SPART cannot be determined for customer 0000006000 , vendor
Diagnosis
No sales organization, distribution channel or division were sent to the IDOC. This data is necessary if a sales order is to be added automatically. If this data is unavailable, you cannot create a sales order document.
I was not able to find the fields to fill the distribution channel and divison in the Idoc structure. I have filled in Sales organization in E1EDK14 segment as 3000.
I am not able to figure out the cause for the error.
Same data works fine from BAPI_SALESORDER_CREATEFROMDAT2.
Please help.
Thanks,
Suma
Edited by: Suma B on Jun 17, 2008 11:12 AM

Hello Suma
In this case I would recommend to debug the IDoc processing.
Call transaction WE19 and start the inbound processing of your IDoc in debugging mode. The error message will most likely occur in function module IDOC_INPUT_ORDERS.
LOOP AT idoc_contrl.
* SET/GET Parameter und interne Tabellen neu initialisieren
* initialize SET/GET Parameter and internal tables
    PERFORM initialize_organizational_data.
* IDOC-Segmente in die entsprechenden Anwendungsdaten übernehmen
* Move IDOC to internal tables
    PERFORM interpret_idoc_orders.                    "<= check here
* Prüfen ob gewisse Segmente gefüllt sind
* check IDOC-Segments
    PERFORM check_idoc_segments.                 "<= check here
* Prüfen und Ermitteln von Organisationsdaten
* check internal tables and determine organization data
Regards
Uwe

Pricing determination for creating sales order using BAPI

Hi,
I am using BAPI_SALESORDER_CREATEFROMDAT2 for creating sales order. I am filling conditions structures
'BAPICOND' and 'BAPICONDX' .
      fs_order_conditions_in-itm_number = '00010'.
      fs_order_conditions_in-cond_type = 'ZNTP'.
      fs_order_conditions_in-cond_value = zsalesinput-price.
      fs_order_conditions_in-currency   = 'INR'.
      append fs_order_conditions_in to order_conditions_in.
      fs_order_conditions_inx-itm_number = '00010'.
      fs_order_conditions_inx-cond_type = 'ZNTP'.
      fs_order_conditions_inx-cond_value = 'X'.
      fs_order_conditions_inx-currency   = 'X'.
     fs_order_conditions_inx-updateflag   = 'U'.
      append fs_order_conditions_inx to order_conditions_inx.
I am filling the conditions table with above mentioned fields.
Sales order is getting created successfully but I am getting two condition records in the conditions tab of sales order, one which is filled using the BAPI and the other one which is automatically picked by the system. Please tell me how to restrict the one which is created automatically by the system.
Because I want the one which is created by BAPI only.
Helpful posts will be rewarded

Hello Manchu.
Basically, it is an SD customizing issue. During the creation of the Sales Order you cannot "restrict" any other condition type. The SD guys must customize the condition type to allow for zero value so that the sales order is successfully created without this conition type.
Regards,
George

Update Reason of Rejection field in Sales Orders

Hi all,
My scenario is:
1) To Close all the open sales orders with a customized Reason of Rejection (ABGRU) field
2) Only when the Sales Order Created Date is 1 month behind the Current Date.
The report program which shall be developed should be run in background and shall automatically close all the Open Sales Orders and update the Reason of Rejection.
Any hints shall be very helpful in addressing ,my problem.
Thanks and Regards
Srikanth.P

Hi,
After prfoeming select query on data base tables , use Bapi BAPI_SALESORDER_CHANGE for updating the reason for rejection and FM RV_SALES_DOCUMENT_UPDATE for updating the status of SO.
Hope this helps you.
BR,
Lokeswari.
Edited by: Lokeswari Bandaru on Sep 27, 2010 9:06 AM

Cannot set item's price in new sales order using E-Commerce for ByDesign.

Hello,
I'm working on a program to create zero value sales orders in my companies SAP system to help track warranties. Every portion of this program is straight forward except for setting an item's list price to zero. I'm using C# .NET. Below is my code to create the SalesOrderMaintainRequestItem. Any advice would be greatly appreciated.
private SalesOrderMaintainRequestItem[] GetItems(Warranty warranty) // Custom Warranty Object
    int count = warranty.LineItems.Count; // Warranty object has an array of line items
    SalesOrderMaintainRequestItem[] item = new SalesOrderMaintainRequestItem[count];
    for (int i = 0; i < count; i++) // for each line item in the warranty object
        item[i] = new SalesOrderMaintainRequestItem();
        item[i].BuyerID = _ID;
        item[i].ItemProduct = new SalesOrderMaintainRequestItemProduct();
        item[i].ItemProduct.ProductID = new NOCONVERSION_ProductID();
        item[i].ItemProduct.ProductID.Value = warranty.LineItems[i].ReplaceWith;
        item[i].PriceAndTaxCalculationItem = new SalesOrderMaintainRequestPriceAndTaxCalculationItem();
        item[i].PriceAndTaxCalculationItem.ItemMainDiscount = new SalesOrderMaintainRequestPriceAndTaxCalculationItemItemMainDiscount();
        item[i].PriceAndTaxCalculationItem.ItemMainDiscount.Rate = new Rate();
        item[i].PriceAndTaxCalculationItem.ItemMainPrice = new SalesOrderMaintainRequestPriceAndTaxCalculationItemItemMainPrice();
        item[i].PriceAndTaxCalculationItem.ItemMainPrice.Rate = new Rate();
        item[i].PriceAndTaxCalculationItem.ItemMainPrice.actionCode = ActionCode.Item01; // tried all the options for this one
        item[i].PriceAndTaxCalculationItem.ItemMainPrice.Rate.DecimalValue = 1.0M; // trying to set it as $1 just for testing, will be 0 when live
           // past tests that didn't work
        //item[i].PriceAndTaxCalculationItem.ItemPriceComponent = new SalesOrderMaintainRequestPriceAndTaxCalculationItemItemPriceComponent[1];
        //item[i].PriceAndTaxCalculationItem.ItemPriceComponent[0] = new SalesOrderMaintainRequestPriceAndTaxCalculationItemItemPriceComponent();
        //item[i].PriceAndTaxCalculationItem.ItemPriceComponent[0].Rate = new Rate();
        //item[i].PriceAndTaxCalculationItem.ItemPriceComponent[0].Rate.BaseDecimalValue = 1.0M;
        //item[i].PriceAndTaxCalculationItem.ItemPriceComponent[0].Rate.DecimalValue = 1.0M;
        //item[i].PriceAndTaxCalculationItem.ItemPriceComponent[0].Rate.CurrencyCode = "USD";
        //item[i].PriceAndTaxCalculationItem.itemPriceComponentListCompleteTransmissionIndicator = true;
        item[i].ItemScheduleLine = new SalesOrderMaintainRequestItemScheduleLine[1];
        item[i].ItemScheduleLine[0] = new SalesOrderMaintainRequestItemScheduleLine();
        item[i].ItemScheduleLine[0].Quantity = new Quantity();
        item[i].ItemScheduleLine[0].Quantity.Value = warranty.LineItems[i].ReplaceQty;
    return item;

Hi Joshua,
it's a long time ago and I hope you were able to solve your issue. For others who want to change prices in sales orders the following might be helpful:
It is not possible to set the price of a sales order in the create webservice call. You need to create the sales order first and then call the webservice a second time with actionCode="02" (Update).
The following is an extract from the sales order webservice documentation:
Node – PriceAndTaxCalculation
A price and tax calculation is the summary of the determined price and tax components for a business case. A specification of the general procedure for price and tax determination and valuation using attributes those are characteristic or relevant for the whole object.
Note: PriceAndTaxCalculation cannot be created but can only be modified. So this means that if the customer wishes to change the Discount or Freight charge, then the customer has to create the order first and then make a second web-service request to the update this sales order with the pricing information that is to be changed.
For the update you only need to send the ID of the sales order, the IDs of the items and the PriceAndTaxCalculation node.
The following would be an easy XML example for the update call:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:glob="http://sap.com/xi/SAPGlobal20/Global">
   <soapenv:Header/>
   <soapenv:Body>
      <glob:SalesOrderBundleMaintainRequest_sync>
         <SalesOrder>
          <ID>1234</ID>
            <Item actionCode="02">
               <ID>10</ID>
               <PriceAndTaxCalculationItem actionCode="02">
                  <ItemMainPrice>
                     <Rate>
                        <DecimalValue>5.00</DecimalValue>
                        <CurrencyCode>USD</CurrencyCode>
                     </Rate>
                  </ItemMainPrice>
               </PriceAndTaxCalculationItem>
            </Item>
         </SalesOrder>
      </glob:SalesOrderBundleMaintainRequest_sync>
   </soapenv:Body>
</soapenv:Envelope>
If you need further help with webservices or C#, let me know.
Best regards,
Felix

System allowing order related Billing for rejected item in sales order

Hi all,
I have created a new reason for rejection: "Billed before Go live"
I have then asigned it to sales item 10 in sales order thus rejecting it.
I expected that when I do the billing for this sales order, the system will not allow to bill the rejected item, but the rejected item is still getting billed by VF01
Can anybody please tell me why this is happening.
Regards,
Avinash Gyale

Hi,
mere reason for rejection is not enough for blocking from billing, at item level you need to put billing block also apart from reason for rejection, then only you can reject the item and block from billing.
thanks ,
gln

Creation of sales order via IDoc ORDERS05 - specify a reason of rejectio

Hi,
I want to create a sales order via IDoc (type:ORDERS05), i specify for an E1EDP01 segment a reason of rejection (ABGRU),
The sales order is created succefully by calling the FM IDOC_INPUT_ORDERS but the order quantity of the item where i have specified a reason of rejection is equals to 0.
Is this normal? i want that this will take 3 value either 0?
Could anyone help me?
Thx

Hi,
Thank you for ur answer.
I've followed the procedure that you have explained and the Quantity 3 have been succefully passed to VA01 but is set to zero when i execute the next OK-CODE (=UER2, i think it is llike Enter button ). I simulate the same procedure by creating a sales order on VA01 and i've finally found the problem : at item level, if i enter the Material (MATNR), the order Quantity (KWMENG) and the Reason of rejection (ABGRU), the quantity is set to zero after clicking the enter button ; but if i enter only The material and The quantity followed by enter button, and enter after the Reason of rejection, it works fine, the Quantity doesn't change.
What is the solution that you propose to me?
I've try this one on debugger mode:
The FM which interpret the Idoc create the sales order by CALLING TRANSACTION 'VA01' USING bdcdata....
I've modified the bdcdata to implement the sequence of the steps before (MATNR + QTY <ENTER> ABGRU <ENTER>).
1. Is it possible to code this modification?
2. Is there a way to structure the Idoc for having this sequence in bdcdata?
Thanks in advance!
Narivelo

Required item no: to populate custom field while creating item for a Sales order

Hello Experts,
I have created a custom field for item data of sales order using AET .
I want to populate this field automatically when ever we create a new item for a sales order using UI or CRMD_ORDER or WCEM by concatenation Sales order number and item number.
We are getting Item GUID but not getting the item number(need item number before getting saved is their any chance to get item number from item GUID ) to populate the field and save it.
For this we tried using BADI's
CRM_BTX_EXTENSIONS
CRM_ORDERADM_I_BADI
Thanks in advance,
Manasa Veena P.

Where did you add the field ?

How to use Bapi for creating sales order

Dear All,
I am facing problem in creating Sales orders using BAPI.
Actually I am getting one file as an input and after validating the contents in the file i am preparing an internal table which has 6 fields - Customer number,PO Number,Material Number,Quantity,Price,Unit of measure.
Now my doubt is that while using BAPI_SALESORDER_CREATEFROMDAT2 , I am not getting how to pass PO Number and Customer number.
Please Help.
Regards,
Shweta

Hi shweta upadhyay
I have gone through you are post i have done some coding for creating sales order using bapi , I think it is helpful for you.
*& Report YOBJ_BAPI_SALESORDER
*& REPORT : CREATING SALES ORDER USING STANDARD BAPI
*& AUTHOR : S.PAVAN KUMAR INUMARTHY
REPORT YOBJ_BAPI_SALESORDER.
DATA : ORDER_HEADER_IN LIKE STANDARD TABLE OF BAPISDHD1 WITH HEADER LINE.
DATA : ORDER_ITEMS_IN LIKE STANDARD TABLE OF BAPISDITM WITH HEADER LINE.
DATA : ORDER_PARTNERS LIKE STANDARD TABLE OF BAPIPARNR WITH HEADER LINE.
DATA : RETURN TYPE STANDARD TABLE OF BAPIRET2 WITH HEADER LINE.
DATA : SALESDOCUMENT LIKE BAPIVBELN-VBELN.
*APPENDING VALUES FOR HEADER.
ORDER_HEADER_IN-DOC_TYPE = 'TA'.
ORDER_HEADER_IN-SALES_ORG = '1000'.
ORDER_HEADER_IN-DISTR_CHAN = '10'.
ORDER_HEADER_IN-DIVISION = '00'.
ORDER_HEADER_IN-SALES_GRP = '130'.
ORDER_HEADER_IN-SALES_OFF = '1030'.
APPEND ORDER_HEADER_IN.
*APPENDING VALUES FOR ITEM
ORDER_ITEMS_IN-MATERIAL = 'M-13'.
ORDER_ITEMS_IN-PLANT = '1000'.
ORDER_ITEMS_IN-SALES_UNIT = 'ST'.
ORDER_ITEMS_IN-DIVISION = '07'.
ORDER_ITEMS_IN-GROSS_WGHT = '28000'.
ORDER_ITEMS_IN-NET_WEIGHT = '28000'.
ORDER_ITEMS_IN-UNTOF_WGHT = 'KG'.
ORDER_ITEMS_IN-VOLUME = '0.780'.
ORDER_ITEMS_IN-VOLUNIT = 'M3'.
APPEND ORDER_ITEMS_IN.
*APPENDING VALUES FOR PARTNER
ORDER_PARTNERS-PARTN_ROLE = 'AG'.
ORDER_PARTNERS-PARTN_NUMB = '0000001000'.
ORDER_PARTNERS-COUNTRY = 'DE'.
ORDER_PARTNERS-TRANSPZONE = 'D000080000'.
APPEND ORDER_PARTNERS.
CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'
EXPORTING
*   SALESDOCUMENTIN               =
    ORDER_HEADER_IN               = ORDER_HEADER_IN
*   ORDER_HEADER_INX              =
*   SENDER                        =
*   BINARY_RELATIONSHIPTYPE       =
*   INT_NUMBER_ASSIGNMENT         =
*   BEHAVE_WHEN_ERROR             =
*   LOGIC_SWITCH                  =
*   TESTRUN                       =
*   CONVERT                       = ' '
IMPORTING
   SALESDOCUMENT                  = SALESDOCUMENT
TABLES
   RETURN                         = RETURN
   ORDER_ITEMS_IN                 = ORDER_ITEMS_IN
*   ORDER_ITEMS_INX               =
    ORDER_PARTNERS                = ORDER_PARTNERS
*   ORDER_SCHEDULES_IN            =
*   ORDER_SCHEDULES_INX           =
*   ORDER_CONDITIONS_IN           =
*   ORDER_CONDITIONS_INX          =
*   ORDER_CFGS_REF                =
*   ORDER_CFGS_INST               =
*   ORDER_CFGS_PART_OF            =
*   ORDER_CFGS_VALUE              =
*   ORDER_CFGS_BLOB               =
*   ORDER_CFGS_VK                 =
*   ORDER_CFGS_REFINST            =
*   ORDER_CCARD                   =
*   ORDER_TEXT                    =
*   ORDER_KEYS                    =
*   EXTENSIONIN                   =
*   PARTNERADDRESSES              =
          IF SY-SUBRC = 0.
          CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
*           EXPORTING
*             WAIT          =
*           IMPORTING
*             RETURN        =
           ENDIF.
WRITE : 'SALES ORDER IS :', SALESDOCUMENT.
This will be very helpful for you .
this one is the correct answer I have tried it and I am posting it for you.
Message was edited by: pavan inumarthy

Custom program for availability check and update for existing sale order at Item level(VA02)

Hi,
I came to know Bapi_Saleorder_Simulate can be used for availability check and update an existing sale order.but there is no sample program explaining the process.I have tried this by passing parameters ORDER_HEADER_IN , ORDER_ITEMS_IN ,ORDER_PARTNERS and ORDER_SCHEDULE_EX(for getting details),also i have assigned the sale document number ,custom document type(ZSO) in ORDER_HEADER_IN . while executing the BAPI I am getting the error external number range is not assigned for the document type ZSO . I am confused on seeing this error. It is possible to do availability check for existing sale order using this BAPI. Please explain how to achieve this.It will be really helpful if it is expalained with an example.
Regards,
Shanmuga

Hello, I think you may have been misinformed about this BAPI updating a sales order at item level. As far as I understand it this BAPI can be used to simulate the creation of a sales order which obviously would include and ATP check. This is why it is giving the error because it is simulating creation but you are entering a value in a field that should be automatically generated (i.e. the sales order number). For change the sales order at item level have you looked at BAPI_SALESORDER_CHANGE? I pretty sure this BAPI both updates sales order (header or item level) and can do an ATP first.
Points are always welcome if you feel an answer has been helpful.

To set reason for rejection for 3rd party order materials

Hello,
I have created the sales order with normal and 3 party materials, with reference to this order i have created the purchase order and delivered normal materials. after some period i am trying to put the reason for rejection code for 3 rd party materials. but the system is showing the error like " subsequent documents already exist for item xyz". then i deleted the purchase requestion and purchase eventhough system is showing the same message while i am trying to put the rejection in the Sales order.
Could you plz let me know the reason why the system is not accepting to put the reason for rejection in the sales order after deleting the PR and PO????
Regards|KS

Hi,
Please refer to SAP note 392945,356895 and 403524.
Thanks and best regards,
Smile

Problem for uplaoding sales text using LSMW

Hi,
I have use LSMW for uplaoding material masters sales and purchase order text , first I have done for purchase order text with object : MATERIAL and ID : BEST it works fine for this after that when I am trying same for uploading sales text OBJECT : MVKE and ID : 0001 it is picking file proerly and till final BDC step it is not giving any error but in material master sales text is not getting updated for that material.
what canb be the problemm
also for pO text for matnr i have given only material code 18 Chr.
and for sales text i hva egiven MATNR + SALES ORG. + DISTRIBUTION CHANNEL as it required for sales text.
regards,
zafar

Dear Zafar,
I found a similar problem while uploading Porduction order long text. May be this information is useful for you.
The common task of changing the long text of a production orderu2019s operation can bring some surprises.
The first problem that is usually encountered is that after updating the long text with the function SAVE_TEXT, the new text is not visible in standard SAP transactions like CO03. The new text can be read with the function READ_TEXT though. The trick is that SAP uses the u201Clong text existsu201D indicator, the field TXTSP in the table AFVC. To make the text u201Cvisibleu201D to standard transactions, we have to set the TXTSP value to the current language (or the textu2019s language). Unfortunately, this has to be done with the direct UPDATE on the AFVC u2013 there are no known workarounds.
Another problem can be seen when the same order is processed by users that use different languages. While SAP allows to store the long text for the same operation in several languages, actually, only one text object will be active at the same time in regard to standard transactions u2013 the object in the last saved language. That means, when SAP writes the text back, the TXTSP will be overwritten with the current language (say, language A). If the next user is working in another language (language B), SAP will present the text in the u201Cfirstu201D language (A) in the CO03 (even if the text in language B exists!). But after saving, the text will be written in the new language and TXTSP will be set accordingly.
So, when working with long texts directly, you have to read with READ_TEXT using the language stored in TXTSP, NOT with the current language. When saving, you save in the current language and set the TXTSP to the current language. This way you are consistent with what SAP does and this will prevent you from surprises in a multilingual environment.
Regards,
Kamal

Problem when setting Reason of Rejection for a sales order using IDOC

Similar Messages

Maybe you are looking for