MRP related message during creation of Sales order

When creating SO, I am getting following messages- " MRP area for material # xxxx not determined, continue with plant MRP area -
", . The system allows me to save the SO, but the message pops up 3 different times- including when it check for ATP. This material has ND for MRP.
How can I suppress this message- where is the config for it? The message no is AG211.
Thanks
Raj

thank you or the info- we are on ECC 6.0- and the notes are from 2001- Would I still need to apply these notes or would they be already applied as part of new version?
Thanks
Raj

Similar Messages

No alternative unit of measure specified, during creation of sales order

Dear Experts,
when user is creating sales order, User is getting the error message no. MM108 "No alternative unit of measure specified" for particular material.
we have checked the alternative unit of measure it is already maintiained in the material master.
we have checked the OSS note : 117611 - Error message MM108 during goods receipt for order, but we couldn't get exact results for our issue.
can you provide the exact reason and solution to over come this please .
Thanks in advance.
Regards,
Suresh Veerepalli

Dear Experts,
The Base Unit of Measure (L) and Sales unit (PCE) ,The alternative unit of measure is maintianed in the material master as shown below.
X AUn Measuremt unit text Y BUn Measuremt unit text
1 L l <=> 1 L l
1.121 KG kg <=> 1.000 L l
1 PCE Piece <=> 1 L l
1 BDL Bundle <=> 12 L l
1 PAL Pallet <=> 720 L l
Error is gettting when creation of Sales Order ,Order is standard order.
When we double click on error message the following details are shown.
1.No alternative unit of measure specified
message no:MM108
2.Diagnosis:
 This alternative unit of measure is missing.
3.System response :
 The system cannot carry out conversion
4.Prodedure:
This is due to Program error that should not occur.
Please provide the exact solution on this issuse.
Thanks

Variant Matching during Creation of Sales Order with reference to Contract

Hi All,
I have a following scenario. Sales Contract is created on a Configurable Material ' A' and its has a Material Variant "B" with following Charac Values X = X1, Y= Y1 & Z=Z1.
The value of Z= Z1 is set using a Procedure when Sales Document Type = OR ( This is the Document type For sales Order). So, this means variant matching will finally happen at Sales Order creation level, coz all the three reqd. charc. are availabe at that time.This is also our reqmt.
But, now what is happening, a Sales Contract is created for Material A, with Charc values X = X1 & Y= Y1. When a sales order is created with reference to this Contract, immediately during Copying of selected item, Variant Matching gets triggered & Material A is replaced by Material Variant B. Even we dont get into the Configuration Window.
Actually, during copying itself Object Depencies are called and thats leading to variant Matching.
Our requirement is that, it should not get triggered at such early stage. It should happen when Config. window is clicked.
Kindly help. Copy Control of Sales Doc has setting 'No Control' We are in ECC 6.0. Are there some other settigs too.
regards,
Stuti

your functional team can help you in finding one.

Error during creation of sales order

while creating a sales order Pricing error, mandatory condition papu is missing...
when i am entering then it shows condition records for condition type papu can only be entered via agreement...pls solve the problem....

Dear Prasanta
Go to VK13, give PAPU and execute so that the system will ask you select a combination. Most probably, you would be maintaining for the combination of "Customer / material with release status". Select that and see whether for that particular customer, pricing is maintained. Since you have not maintained the pricing for that customer and material, you are facing the problem. Maintain price and then retry.
thanks
G. Lakshmipathi

Message No V 0102 (Sales Order Error During Saving)

We are using SAP ECC 6 version and the client is related to Beverage Industry.
Problem:
The scenario is this that we created a Sales Order. In the Sales Order we have entered let say 20 items and the item have sub item as well. We are using BOM usage 5. Once the order is confirmed the user creates the Delivery Order but doesnt Post the Good Issue.
Now the requirement is that the user wants to change and delete some item in sales order.
For this first we amend the delivery order and then we change the sales order according the amendments made in Delivery Order.
In this scenario we also want to completely delete the Main item but as its default that the Bom item will be deleted with the main but we want to enter the sub item again in the order because its the process requirement.
Now when I make all the necessary changes in Delivery Order and Sales Order Respectively System saves the Delivery order with the changes values but gives an error message after Saving the Sales Order and doesnt update the Sales Order as well
Attached are the Screen Shot of Sales Order Error Screen.
Note: This Error comes randomly

Refer OSS 740280

Creation of Sales Order and Service Contract from Inbound IDOC

Hi Experts,
My requirement is to create a Sales Order as well as a Service Contract from one Inbound IDOC. I am getting the Inbound IDOC from a third Party. The message type is ORDERS and Basic Type is ORDERS02. How ever i am using an extension type IDOC which carries all the required data for Sales Order and Service Contract. My requirement is like, to create a Sales Order first.
I have created a Z FM which is attached to the Process Code and subsequently to the message type. Inside the FM i an calling FM 'IDOC_INPUT_ORDERS' for creation of Sales Order. After that i am changing the IDOC data for the Document Type. I am changing the document type which is responsible for Contract Creation.
Then I am again calling the FM 'IDOC_INPUT_ORDERS' for creation of Contract with the help of IDOC data. But here the Contract is not getting created. It's getting failed during the Batch input session.
I need to solve this problem as soon as possible. Please help me. If there are any other options also please share.
Thanks in Advance.
Regards,
Priyabrata

Actually there is problem with BDCDATA. Inside the FM it's calling transaction with help of BDCDATA. If i am creating a Sales order or contract alone its creating successfully. But when i am trying to create both, it's retuning sy-subrc '1001' after calling the transaction on the second attempt. Is there any problem with BDCDATA like we can't handle with less time gap? Please help and give your inputs.
Regards,
Priyabrata

Va01 creation of sales order

Hi
can i create sub screen in creation of sales order item
in user exit mv45afzz
my requirement is when user click on any line item than than i need to call subscreen with some information
pls guide me on this

HI

Sales realated exits
SDTRM001 Reschedule schedule lines without a new ATP check
V45A0001 Determine alternative materials for product selection
V45A0002 Predefine sold-to party in sales document
V45A0003 Collector for customer function modulpool MV45A
V45A0004 Copy packing proposal
V45E0001 Update the purchase order from the sales order
V45E0002 Data transfer in procurement elements (PRreq., assembly)
V45L0001 SD component supplier processing (customer enhancements)
V45P0001 SD customer function for cross-company code sales
V45S0001 Update sales document from configuration
V45S0003 MRP-relevance for incomplete configuration
V45S0004 Effectivity type in sales order
V45W0001 SD Service Management: Forward Contract Data to Item
V46H0001 SD Customer functions for resource-related billing
V60F0001 SD Billing plan (customer enhancement) diff. to billing plan
V46H0001 SD Customer functions for resource-related billing
V45W0001 SD Service Management: Forward Contract Data to Item
V45S0004 Effectivity type in sales order
V45S0003 MRP-relevance for incomplete configuration
V45S0001 Update sales document from configuration
V45P0001 SD customer function for cross-company code sales
V45L0001 SD component supplier processing (customer enhancements)
V45E0002 Data transfer in procurement elements (PRreq., assembly)
V45E0001 Update the purchase order from the sales order
V45A0004 Copy packing proposal
V45A0003 Collector for customer function modulpool MV45A
V45A0002 Predefine sold-to party in sales document
V45A0001 Determine alternative materials for product selection
SDTRM001 Reschedule schedule lines without a new ATP check
SDAPO001 Activating Sourcing Subitem Quantity Propagation
https://www.sdn.sap.com/irj/sdn/wiki
Check this link
Sail

HOW TO CONTROL ON CREATION OF SALES ORDER WITH REFERENCE TO EARLIER SO?

Dear All,
I want to contol on creation of Sales order with reference to earlier SO? While creation of sales order our enduser are creating sales order with reference to earlier month SO which I want to restrict. Recently I made changes in sales order like payment terms is grayed, system will atomatically pick pay terms from customer master.Now I am getting correct data also but enduser is using old SO no while creating new SO and old payment data is reflecting in fbl5n.
I want to restrict enduser while creating new SO with ref. to old SO. Only for returns they should be able to use Billing refrence. Pl. suggest how to control the with reference to ealier SO.
Nikhil

Nikhil Deshpande,
If you dont want allow create a sales order in referent to other one, just delete the copy control between these sales order type, so when the user tries to create a SO in reference to other one a message is displayed that is not possible.
Thanks,
Mariano.

Issue with creation of sales order in CRM system

Hi Experts,
Here are the details of the process we followed
1.     We found a Function Module u201CBAPI_BUSPROCESSND_CREATEMULTIu201D which is used to create a sales order in CRM.
2.     We have set a Break point in the FM u201CCRM_ORDER_MAINTAINu201D and tried to create a sales order using the transaction u201CCRMD_ORDERu201D. For this the parameters we have given are
a.     sold-to-party
b.     ship-to-party
c.     quantity
d.     product
And after this we have saved the order and the order is saved and in the debug mode we have the parameters in u201CCRM_ORDER_MAINTAINu201D and we found all these     parameters in the FM.
3.     After this we have given all the parameters mentioned above in the FM u201CBAPI_BUSPROCESSND_CREATEMULTIu201D and still the order is not created, gave an error message saying that CRM_ORDER: Incorrect values in the interface object.
4.     We checked the CRM_ORDER badiu2019s interface and it is having only header guid to be given. We gave this header guid also in the FM u201CBAPI_BUSPROCESSND_CREATEMULTIu201D and then it gave a different error saying that : Document cannot be saved.
5.     Finally we are not able to know the parameters to be passed to the FM to create an order.
Any inputs will be highly appreciated.
Thanks a lot in advance.
Lakshman.

Hi Easwar,
Now i am able to create a sales order by passing the parameters to "BAPI_BUSPROCESSND_CREATEMULTI" and the parameters i am passing are Process_type in the ORDERADM_H, parner_fct (partner function), partner_no , Quantity and prod_ordered (product name) but after creation of sales order using my report program and if i see the sales order uisng transaction crmd_order (using transaction ID) or crmd_orderadm_h(using headerguid) or crm_order_index, only the PROCESS_TYPE is updated but the remaining parameters which i passed like QUANTITY,PRODUCT NAME,PARTNER NUMBER are not present in the sales order. I am providing the code which i have written for creation of the sales order. Can you please look into it and tell me where i might have went wrong??
*& Report ZCREATEORDER_TEST
REPORT ZCREATEORDER_TEST.
DATA : LV_HEADER_GUID TYPE GUID_32,
WA_HEADER            TYPE         BAPIBUS20001_HEADER_INS,
ITAB_HEADER          TYPE STANDARD TABLE OF BAPIBUS20001_HEADER_INS,
ITAB_CREATED_PROCESS TYPE STANDARD TABLE OF BAPIBUS20001_HEADER_INS,
ITAB_OBJECTS_TO_SAVE TYPE STANDARD TABLE OF BAPIBUS20001_GUID_DIS,
ITAB_PARTNER        TYPE STANDARD TABLE OF BAPIBUS20001_PARTNER_INS,
lt_product_i TYPE STANDARD TABLE OF BAPIBUS20001_ITEM,
wa_product_i type BAPIBUS20001_ITEM,
lt_schedlin_i type standard table of BAPIBUS20001_SCHEDLIN,
wa_schedlin_i type BAPIBUS20001_SCHEDLIN,
ITAB_INPUT_FIELDS TYPE TABLE OF bapibus20001_input_fields,
ls_inputfields TYPE bapibus20001_input_fields,
WA_PARTNER          TYPE BAPIBUS20001_PARTNER_INS,
ITAB_RETURN          TYPE STANDARD TABLE OF BAPIRET2,
WA_OBJECTS_TO_SAVE LIKE LINE OF ITAB_OBJECTS_TO_SAVE,
           "To store the Objects to be saved.
WA_CREATED_PROCESS LIKE LINE OF ITAB_CREATED_PROCESS,
ITAB_SAVED_OBJECTS   TYPE STANDARD TABLE OF BAPIBUS20001_OBJECT_ID,
WA_SAVED_OBJECTS    LIKE LINE OF ITAB_SAVED_OBJECTS,
GC_X type c.
gc_x = 'x'.
CALL FUNCTION 'GUID_CREATE'
IMPORTING
    ev_guid_32 = lv_header_guid.
CLEAR : WA_HEADER.
Passing the respective values from the Header table to internal table.
WA_HEADER-GUID          = LV_HEADER_GUID.
WA_HEADER-PROCESS_TYPE = 'ZTA'.
APPEND WA_HEADER TO ITAB_HEADER.
*Appending the values to the ITAB_HEADER.
ls_inputfields-ref_guid = LV_HEADER_GUID.
ls_inputfields-REF_KIND = 'A'.
ls_inputfields-objectname = 'ORDERADM_H'.
ls_inputfields-logical_key = ' '.
ls_inputfields-fieldname = 'PROCESS_TYPE'.
APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
*ls_inputfields-ref_handle = '0000000000'.
ls_inputfields-ref_guid = LV_HEADER_GUID.
ls_inputfields-objectname = 'ORDERADM_H'.
ls_inputfields-fieldname = 'MODE'.
APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
ls_inputfields-ref_guid = LV_HEADER_GUID.
ls_inputfields-REF_KIND = 'A'.
ls_inputfields-objectname = 'ORDERADM_H'.
ls_inputfields-logical_key = ' '.
ls_inputfields-fieldname = 'GUID'.
APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
CHANGES MADE
ls_inputfields-ref_guid = LV_HEADER_GUID.
ls_inputfields-REF_KIND = 'A'.
ls_inputfields-objectname = 'SCHEDLIN'.
ls_inputfields-logical_key = ' '.
ls_inputfields-fieldname = 'LOGICAL_KEY'.
APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
ls_inputfields-ref_guid = LV_HEADER_GUID.
ls_inputfields-REF_KIND = 'A'.
ls_inputfields-objectname = 'SCHEDLIN'.
ls_inputfields-logical_key = ' '.
ls_inputfields-fieldname = 'MODE'.
APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
ls_inputfields-ref_guid = LV_HEADER_GUID.
ls_inputfields-REF_KIND = 'A'.
ls_inputfields-objectname = 'SCHEDLIN_I'.
ls_inputfields-logical_key = ' '.
ls_inputfields-fieldname = 'GUID'.
APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
   ls_inputfields-ref_guid = LV_HEADER_GUID.
ls_inputfields-REF_KIND = 'A'.
ls_inputfields-objectname = 'SCHEDLIN_I'.
ls_inputfields-logical_key = ' '.
ls_inputfields-fieldname = 'QUANTITY'.
APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
   ls_inputfields-ref_guid = LV_HEADER_GUID.
ls_inputfields-REF_KIND = 'A'.
ls_inputfields-objectname = 'SCHEDLIN_I'.
ls_inputfields-logical_key = ' '.
ls_inputfields-fieldname = 'MODE'.
APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
CHANGES MADE
WA_PARTNER-REF_GUID = LV_HEADER_GUID.
WA_PARTNER-REF_KIND = 'A'.
giving the partner function and partner no 000000038 for slod to party
WA_PARTNER-PARTNER_FCT = '00000038'.
WA_PARTNER-PARTNER_NO = '10017'.
APPEND WA_PARTNER TO ITAB_PARTNER.
*"ADDING VALUES for the product
wa_product_i-header        = lv_header_guid.
wa_product_i-handle        = '0000000001'.
wa_product_i-ordered_prod = '12000014'.
wa_product_i-mode          = 'A'.
APPEND wa_product_i TO lt_product_i.
*"ADDING VALUES for quantity
wa_schedlin_i-quantity   = 30.
wa_schedlin_i-handle = 1.
APPEND wa_schedlin_i TO lt_schedlin_i.
ls_inputfields-ref_guid = LV_HEADER_GUID.
ls_inputfields-REF_KIND = 'A'.
ls_inputfields-objectname = 'PARTNER'.
*ls_inputfields-logical_key = ' '.
ls_inputfields-fieldname = 'REF_GUID'.
APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
ls_inputfields-ref_guid = LV_HEADER_GUID.
ls_inputfields-REF_KIND = 'A'.
ls_inputfields-objectname = 'PARTNER'.
ls_inputfields-logical_key = ' '.
ls_inputfields-fieldname = 'PARTNER_FCT'.
APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
ls_inputfields-ref_guid = LV_HEADER_GUID.
ls_inputfields-REF_KIND = 'A'.
ls_inputfields-objectname = 'PARTNER'.
ls_inputfields-logical_key = ' '.
ls_inputfields-fieldname = 'PARTNER_NO'.
APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
CALL FUNCTION 'BAPI_BUSPROCESSND_CREATEMULTI'
TABLES
    HEADER          = ITAB_HEADER
    ITEM            = lt_product_i
    RETURN          = ITAB_RETURN
    PARTNER         = ITAB_PARTNER
    INPUT_FIELDS    = ITAB_INPUT_FIELDS
    CREATED_PROCESS = itab_created_process
    SCHEDULELINE    = lt_schedlin_i.
READ TABLE ITAB_CREATED_PROCESS INTO WA_CREATED_PROCESS WITH KEY GUID = LV_HEADER_GUID BINARY SEARCH.
WA_OBJECTS_TO_SAVE-GUID = WA_CREATED_PROCESS-GUID.
Appending the Guid of the contract to be saved to the internal table
APPEND WA_OBJECTS_TO_SAVE TO ITAB_OBJECTS_TO_SAVE.
CALL FUNCTION 'BAPI_BUSPROCESSND_SAVE'
EXPORTING
    update_task_local = space
    save_frame_log    = GC_X
TABLES
    objects_to_save   = itab_objects_to_save
    saved_objects     = itab_saved_objects
    return            = itab_return.
Calling the Standard BAPI to Commit the transcation.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
I have debugged the above code, all the values are passing are passing to the FM "'BAPI_BUSPROCESSND_CREATEMULTI'" and these passed to the CRM_ORDER_MAINTAIN and then to CRM_ORDER_READ which are called inside the "'BAPI_BUSPROCESSND_CREATEMULTI'". Finally the sales order is created but not able to see all the values that i am passing except PROCESS_TYPE.
Thanks a lot in Advance,
Lakshman.

Error during creation of transfer orders for material

Hi,
We are doing a transfer of stock from one storage with WM to a storage without WM.
But system does not finish the process automatically displaing the following error message:
"Error during creation of transfer orders for material document 49000XXXX"
System cannot find source storage bin
Thanks in advance for the help
Regard
Enzo

your picking strategy does not find the bin where the material is.
So you need to check what value you have entered for picking in WM view of material master.
then you have to check where your material is (storage type and bin)
then you need to check customizing to where what storage types are included in the picking strategy that is tight to the material master entry.

Change Production version during creation of Process Order COR1

Hi,
Scenario:
Based on the entered Material, Plant and Order type system need to trigger a popup asking the user to select the Production Version. This should happen before clicking on SAVE button, so that all the values will be populated correctly based on the changed VERID.
I did not find a user exit that enables to change the Production Version (VERID) value. So I thought of displaying the popup in the user exit EXIT_SAPLCOZF_003 which will be triggered before initial screen appears, export the selected value and pass it to a User Exit or BADI where VERID can be changed. But cannot find a user exit to do it.
Please help me find a User Exit or BADI to change the Production Version during creation of Process Order using COR1 transaction before clicking on SAVE button.
Thanks,
Manoj.

Hi Manoj,
So - almost four years later - I saw your post and I saw myself in the very same situation as you did...
I found a solution for those who wants to change the production version of the production order from the sales order creation: create an enhancement in the function module 'MD_VERSION_SELECTION' and you are good to go.

No commitment Item Update while creation of Sales order

hi,
I have maintained Derivation Rule
Co Code / GL/ BA/ Plant / S Loc/ = Fund / Comitement / Fund Center.
Stil in that case at the time of creation of Sales order, systeme is giving error (++No commitment Item Update M V2225++)
And also i have maintained the Comitement Item in GL master.
Could you give me some solution.
Thanks
Nilesh R

Hi Nilesh R,
Please check the following information of Consulting Note 1268001 (the same for funds center is valid to commitment item):
1. You receive the error message in a Sales Order (SD) process.
   a) SD customizing settings for FM objects.
   You can set "commitment item" as an optional entry in SD customizing settings for field status. This can be checked in the IMG path: SPRO -> Public Sector Management -> Funds Management Government-> Actual and Commitment Update/Integration -> Integration ->
   Maintain Field Status for Assigning FM Account Assignments
   You should have a record with Object type = '04' (sales order).
   It is not necessary to have the field as required (unless you want to insert it in the origin process) due to the fact that
   this can avoid the account assignment derivation between CO objects and FM objects. The field can not be hidden otherwise it will be not derived.
   For more information, check note 572729.
The system response depends on how you defined the fields of the FM dialog box using Customizing activity 'Maintain Field Status for Assigning FM Account Assignments':
     - The fields of the FM dialog box are defined as ready for input ('Opt. entry' or 'Req. entry') in Customizing:
        If you change the reference object in the sales order, the system does not re-derive FM data automatically. For that, you
        must navigate to the FM dialog box and, by choosing icon 'Redetermine account (F5)', trigger the derivation manually.
     -   The fields of the FM dialog box are defined as not changeable ('Display') in Customizing:
         If the reference object is changed in the order, FM data is redetermined automatically.
     - The fields of the FM dialog box are defined as not displayable ('Hide') in Customizing:
         FM data is not determined.
Therefore, set the field status to optional permit the user to enter the FM objects manually and still benefit from the possibility to
automatically derive the FM objects from a CO object.
For more information on integrating Plant Maintenance, Sales and Distribution and Project System, see the SAP Library Accounting -> Public Sector Management -> Funds Management -> Actual and Commitment Update -> Integration with Plant Maintenance, Integration with Sales and Distribution and Integration with Project System (Network).
You can also check the documentation available in the IMG menu of the status (written above).
   b) If you do not want to integrate sales order process within PSM-FM, you should consider to deactivate this integration in
      customizing transaction OFUP. In release EA-PS 1.10 and 2.00 modification note 591573 is available.
Please also check consulting note 1267998 and let me know if you have used FMDERIVE trace tool.
If you want to have SD integrated to FM, please check if in OFUP the flag of this integration is accordingly set.
If you work with free-of-charge sales order line items mixed with line items having value, please consider to apply note 1441847 (if it is valid to your current release/package).
I hope this answer your inquiry.
Best Regards,
Vanessa Barth.

TCODE for Process order creation against Sales order

Hi gurus,
Pls tell me what is the TCODE for Process order creation against Sales order
Eg. CO07 is for production order from sales orde

Typically, in MTO scenario after the sales order is created you run MRP which will create planned order and then you convert that into production order using MD04.
Or if you have SD settings correctly directly from the release of Sales Order it will create planned order or production order.
please check and revert back.

!How to find out follow up activities created during creation of an Order??

Hi Gurus,
I want to find out the number of follow up activities created during creation of an Order??
Is there any BAPI or Function Module which can detrmine the number of follow up activities after creation / saving an Order..
Please Reply fast.
Thanks
Pranay

Hi Pranav,
I am confident this will solve your problem:
Step 1.
Enter the guid of the current order into function module
CRM_DOC_FLOW_READ_DB.
Code:
DATA : t_doc_links TYPE crmt_doc_flow_db_wrkt,
 v_guid TYPE crmt_object_guid.
v_guid = <guid of the order from table crmd_orderadm_h>
CALL FUNCTION 'CRM_DOC_FLOW_READ_DB'
 EXPORTING
 iv_header_guid = v_guid
 IMPORTING
 et_doc_links = t_doc_links
 EXCEPTIONS
 error_occurred = 1
 OTHERS = 2.
Step2.
Now loop through the returned table ie t_doc_links.
Records which fulfill the following criteria are
the follow up records.
reltype = 'VONA'
objtype_b = 'BUS2000126'
objkey_b = v_temp
roletype_b = 'NACHFOLGER'
roletype_a = 'VORGAENGER'.
Step:3
Now Count the records which fulfill the above creteria.
This count represent the number of followups created.
REWARD THE ANSWER WITH FULL 10 POINTS IF UR PROBLEM IS SOLVED.
thanks,
ashish.

Blocking RdA creation from Sales Order Schedule Line

Hi Gurus,
please do you know if there is a way to block the RdA creation from Sales Order schedule line, for TAS item category? I tried with Header Delivery block without quantity confirmation but even if quantity on schedule lines are not confirmed, RdA is created anyway.
Thank you very much
Kind Regards
Andrea

thank you

MRP related message during creation of Sales order

Similar Messages

Maybe you are looking for