Sales order to automatically create assembly order

Hi one and all,
How to set up a system to be able to choose materail requriment transferred from sales order to automatically create an assembly order, a planned order, and a process order?

Hi,
Assigh the repective Planning startegy group at MRP view of material Master.
81 - Assembly porcessing for planned order
82 - Assembly porcessing for production order.
86 - Assembly porcessing for Process order
Try with this and crate Sale order.
Regards
PradeeP

Similar Messages

Ps assembly processing:WBS have not be created when saving the sales order

In the ps assembly processing, I want to generate a network when I create a sales order. So I did the following steps:
1-Use the TCODE cj91 to create a standard WBS "E-000007.1".
2-Use the TCODE cn01 to create a standard network "10000000" and assign the standard WBS "E-000007.1" to it.
3-Use the TCODE cn08 to config the Network Parameters from Sales Order like below:
Material number : 600000-000000-0009
Order Type      : Z301
Std network     : 10000000
Class Type      : 020
Network Profile : Z0001
MRP Controller : 001
Std WBS element : E-000007.1
4-Use the TCODE va01 to create a sales order and add an item with the material "600000-000000-0009" and save.
    When the SAP R/3 System is saving the sales order, a WBS ought to be created u2013 based on the assignment of the standard network to the standard project.But I could not found the WBS.I thought I have do all of steps and could not found the reason.
   So I need the experts give me some useful advice and reference to resolve the problem.Thank you.
Regards
Yoda

Hi,
Maintain strategy group in material master MRP tab....
If problem still persist then check is there any credit block to that customer...if it is release it in VKM3....
Once you release it will create automatically.
Regards

Creating a Service Order automatically when saving a Sales Order

Hello SDN,
I'm trying to have SAP automatically create a Service Order when a Sales Order is created. To this end, I've tried implementing BADI workitem_template and have been using method before_update. I've been using BAPI BAPI_ALM_ORDER_MAINTAIN to create the service order.
The problem is that in order for the BAPI to save the service order, the sales order needs to be fully saved and operational. Otherwise it just keeps saying 'sales order does not exist'. So the problem is that the BADI is intervening too soon in the saving process. The temporary sales order numbers have been replaced with actual ones, but the records do not show in the database just yet. I think there's a commit that still needs to be done or something.
However, I cannot find a BADI or user exit that intervenes after the sales order is saved into the database, so this leaves me stranded.
Any suggestions would be heartily apprechiated.
Kind Regards,
Niels.
Edited by: Niels Ruelens on Feb 20, 2008 4:20 PM
Edited by: Niels Ruelens on Feb 20, 2008 4:22 PM

Following your suggestions, I've created an update function module and inserted it into the USEREXIT_SAVE_DOCUMENT. In this function module, I'm calling the BAPI.
Problem with this approach is that I cannot debug, nor is he actually doing anything. Here's the code that is put in the function. Is there anything wrong with the way I call the BAPI perhaps?
DATA:
    lt_srule     TYPE TABLE OF bapi_alm_order_srule,
    lt_bheader   TYPE TABLE OF bapi_alm_order_headers_i,
    lt_srule_up TYPE TABLE OF bapi_alm_order_srule_up,
    lt_methods   TYPE TABLE OF bapi_alm_order_method,
    lt_return    TYPE TABLE OF bapiret2,
    ls_vbak      TYPE vbak,
    ls_vbap      TYPE vbap,
    ls_bheader   TYPE bapi_alm_order_headers_i,
*    ls_header    TYPE cobai_s_header,
    ls_prps      TYPE prps,
    ls_srule     TYPE bapi_alm_order_srule,
    ls_srule_up TYPE bapi_alm_order_srule_up,
    ls_methods   TYPE bapi_alm_order_method.
*    ls_item      TYPE cobai_s_item.
SELECT SINGLE * INTO ls_vbak
FROM vbak
WHERE vbeln = vbeln.
SELECT SINGLE * INTO ls_vbap
FROM vbap
WHERE vbeln = vbeln.
FREE: lt_methods, lt_bheader, lt_srule.
* Fill methods
CLEAR ls_methods.
ls_methods-refnumber = 1.
ls_methods-objecttype = 'HEADER'.
ls_methods-method     = 'CREATE'.
ls_methods-objectkey = '%00000000001'.
APPEND ls_methods TO lt_methods.
* CLEAR ls_methods.
* ls_methods-refnumber = 1.
* ls_methods-objecttype = 'SRULE'.
* ls_methods-method     = 'CREATE'.
* ls_methods-objectkey = '%00000000001'.
* APPEND ls_methods TO lt_methods.
CLEAR ls_methods.
ls_methods-refnumber = 1.
ls_methods-objecttype = ''.
ls_methods-method     = 'SAVE'.
ls_methods-objectkey = '%00000000001'.
APPEND ls_methods TO lt_methods.
* Fill header
CLEAR ls_bheader.
ls_bheader-orderid    = '%00000000001'.
ls_bheader-order_type = 'ZM02'.
ls_bheader-funct_loc = 'FERBL_TD5C_DER'.
ls_bheader-planplant = 'B006'.
ls_bheader-sales_ord = vbeln.
ls_bheader-s_ord_item = '00010'.
APPEND ls_bheader TO lt_bheader.
** Convert the internal WBS to an external WBS element
* SELECT SINGLE * INTO ls_prps
* FROM prps
* WHERE pspnr = ls_vbap-ps_psp_pnr.
**   Fill settlement rules
* ls_srule-objnr =   ls_item-aufnr.
****    ls_srule-sales_ord = caufvd_imp-kdauf_aufk.
****    ls_srule-s_ord_item = caufvd_imp-kdpos_aufk.
* ls_srule-wbs_element = ls_item-projn.
* ls_srule-settl_type = 'FUL'.
* ls_srule-percentage = 100.
* ls_srule-extnr = 1.
* APPEND ls_srule TO lt_srule.
* ls_srule_up-wbs_element = 'X'.
* ls_srule_up-sales_ord = 'X'.
* ls_srule_up-s_ord_item = 'X'.
* ls_srule_up-orderid = 'X'.
* ls_srule_up-settl_type = 'X'.
* ls_srule_up-percentage = 'X'.
* ls_srule_up-extnr = 'X'.
* APPEND ls_srule_up TO lt_srule_up.
CALL FUNCTION 'BAPI_ALM_ORDER_MAINTAIN'
    TABLES
      it_methods              = lt_methods
      it_header               = lt_bheader
*          IT_HEADER_UP            =
*          IT_HEADER_SRV           =
*          IT_HEADER_SRV_UP        =
*          IT_USERSTATUS           =
*          IT_PARTNER              =
*          IT_PARTNER_UP           =
*          IT_OPERATION            =
*          IT_OPERATION_UP         =
*          IT_RELATION             =
*          IT_RELATION_UP          =
*          IT_COMPONENT            =
*          IT_COMPONENT_UP         =
*          IT_OBJECTLIST           =
*          IT_OBJECTLIST_UP        =
*          IT_OLIST_RELATION       =
*          IT_TEXT                 =
*          IT_TEXT_LINES           =
*     it_srule                = lt_srule
*     it_srule_up             = lt_srule_up
*          IT_TASKLISTS            =
*          EXTENSION_IN            =
         return                  = lt_return.
*          ET_NUMBERS              =.
IF sy-subrc = 0.
ENDIF.
Edited by: Niels Ruelens on Feb 20, 2008 4:58 PM

Automatic Sales order should be raised once a po is created

Hi Guys,
There are two company codes 1000 and 2000
when a p.o.is raised by company code 1000 in the back ground it should raise a salesoreder in the other company code 2000.
What are the settings that to be done?
Thanks & Regards,
Suresh.

Hi
The below steps can help you to create PO automatically after sales order is saved.
1. Set up back-to-back, i.e. PR can be automatically created after the SO is saved.
2. Item category - make sure 'Create PO automatically' checkbox is ticked.
3. Enterprise Structure --> Sales Organization - ensure that PO type, purchasing group etc. is maintained.
4. Transaction code SWETYPV - Ensure that both checkboxes are ticked for BO (object category), BUS2032 (object type), ALECREATEE/CHANGED and ERRORCHANGINGPURORD/ERRORCREATINGPURORD.
5. Optional: You could execute BD86 to check for consistencies (note that you can still get it work even if BD86 shows errors).
Regards,
BK

Free of goods should come automatically back when creates return sales order

Dear sd experts
I Know one thing that free goods wont come back ,, for ex when we create return sales order free goods wont come bz in VTAF copy requirement 302
it means dont copy free goods
Now i went VOV7--- for item category TANN-- i have maintained billing relevance A it means free goods items will come in to billing
now when i am creating return sales order with reference to billing Free goods are not coming
My doubt is suppose if my clinte asks free goods will come automatically when creates returns how to do it ?

Hi Ali,
I just checked and understand in the below way:
When I Do the PGI system is posting say 50 USD to COGS. But, when I do the Invoice ( 100 USD is credited to sales account and 100 is debited to discount account) So at the end 100 is getting Nullified. But, when we see P&L account you will COGS of 50 USD.
I checked along with my FI consultant and she confirmed that its posting as per expected way only.
Let me know if you need more details here.
Regards, Sai Krishna.

Automatic creation of settlement rule while creating sales order

Hi Friends,
Can any one help me how to create settlement rule automatically while creating sales order i.e saving sales order. Is there any function module or any badi which can be used.. please suggest.
thanks
bobby

Hi,
Here is the solution , First Create a sustitution by going into OPSN Transaction , only user exit say 'U902'
and write the form routine in Program named 'ZRGGBS000'
The code is below ,
*&      Form U902
   Automatic Generation of Settlement Rule For WBS and Company 4180
FORM u902.
Exit For Automatic Settlement Rule Creation for WBS Billing elements
IF sy-tcode = 'CJ20N' or sy-tcode = 'CJ01' or sy-tcode = 'CJ02'.
    DATA   lv_proj TYPE ps_pspid.
    lv_proj = proj-pspid.
    EXPORT lv_proj TO MEMORY ID 'PSPID'.
Calling YGPS_CJB1EXEC Program For Creating Settlement Rule
    SUBMIT ygps_cjb1exec AND RETURN.
ENDIF.
ENDFORM.                                                    "u902
*& Program YGPS_CJB1EXEC
PROGRAM ygps_cjb1exec.
   Automatic Generation of Settlement Rule For WBS and Company 4180
Called From Exit For Automatic Settlement Rule Creation for WBS Billing elements
DATA: bdcdata_wa TYPE bdcdata,
      bdcdata_tab TYPE TABLE OF bdcdata,
      itab TYPE TABLE OF bdcmsgcoll.
DATA :lv_currm LIKE bkpf-monat,
      lv_curry LIKE bkpf-gjahr,
      lv_prevm LIKE bkpf-monat,
      lv_prevy LIKE bkpf-gjahr,
      lv_proj TYPE ps_pspid,
      lv_mode TYPE c,
      lv_time TYPE sy-uzeit.
DATA :g_datfm            LIKE usr01-datfm,
      g_dd(2)            TYPE c,                         " Day
      g_mm(2)            TYPE c,                         " Month
      g_yyyy(4)          TYPE c,                         " Year
      g_sydatum(10)      TYPE c.
IMPORT lv_proj FROM MEMORY ID 'PSPID'.
lv_mode = 'N'.
CLEAR bdcdata_wa.
bdcdata_wa-program = 'SAPLKAZB'.
bdcdata_wa-dynpro   = '1000'.
bdcdata_wa-dynbegin = 'X'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'BDC_CURSOR'.
bdcdata_wa-fval = 'PRZB-VARIANT'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'PRZB-VARIANT'.
bdcdata_wa-fval = 'ZGPS0001'.
APPEND bdcdata_wa TO bdcdata_tab.
CALL FUNCTION 'GET_CURRENT_YEAR'
EXPORTING
    bukrs = '4180'
IMPORTING
    currm = lv_currm
    curry = lv_curry
    prevm = lv_prevm
    prevy = lv_prevy.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'RKAUF-FROM'.
bdcdata_wa-fval = lv_currm.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'RKAUF-GJAHR'.
bdcdata_wa-fval = lv_curry.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'BDC_OKCODE'.
bdcdata_wa-fval = '=VARC'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-program = 'RKPSEL00'.
bdcdata_wa-dynpro   = '1000'.
bdcdata_wa-dynbegin = 'X'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'BDC_CURSOR'.
bdcdata_wa-fval = 'CN_PROJN-LOW'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'CN_PROJN-LOW'.
bdcdata_wa-fval = lv_proj.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'CN_PSPNR-LOW'.
bdcdata_wa-fval = space.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'CN_NETNR-LOW'.
bdcdata_wa-fval = space.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'CN_ACTVT-LOW'.
bdcdata_wa-fval = space.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'CN_MATNR-LOW'.
bdcdata_wa-fval = space.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'BDC_OKCODE'.
bdcdata_wa-fval = '/00'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'BDC_OKCODE'.
bdcdata_wa-fval = '=SAVE'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'BDC_OKCODE'.
bdcdata_wa-fval = '=VBAC'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-program = 'SAPLSPO1'.
bdcdata_wa-dynpro   = '0100'.
bdcdata_wa-dynbegin = 'X'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'BDC_OKCODE'.
bdcdata_wa-fval = '=YES'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-program = 'SAPLKAZB'.
bdcdata_wa-dynpro   = '1000'.
bdcdata_wa-dynbegin = 'X'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'RKAUF-BATCH'.
bdcdata_wa-fval = 'X'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'RKAUF-TEST'.
bdcdata_wa-fval = space.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'BDC_OKCODE'.
bdcdata_wa-fval = '=RUN'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-program = 'SAPLKABA'.
bdcdata_wa-dynpro   = '0210'.
bdcdata_wa-dynbegin = 'X'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'KABA01-JNAME'.
bdcdata_wa-fval = 'CJB1_EXEC'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'BDC_SUBSCR'.
bdcdata_wa-fval = 'SAPLKABA'.
APPEND bdcdata_wa TO bdcdata_tab.
Extract the date format from the user settings
PERFORM f_get_dateformat CHANGING g_datfm.
Changing the current date format to User Profile Date Settings
PERFORM f_format_date USING   g_datfm
                              sy-datum+4(2)
                              sy-datum+6(2)
                              sy-datum+0(4)
                     CHANGING g_sydatum.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'KABA01-STDAY'.
bdcdata_wa-fval = g_sydatum.
APPEND bdcdata_wa TO bdcdata_tab.
lv_time = sy-uzeit + 30.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'KABA01-STTME'.
bdcdata_wa-fval = lv_time.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'KABA01-PRIKZ'.
bdcdata_wa-fval = space.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'BDC_OKCODE'.
bdcdata_wa-fval = '=TAKE'.
APPEND bdcdata_wa TO bdcdata_tab.
Calling Transaction 'CJB1' for creating settlement rule
CALL TRANSACTION 'CJB1' USING bdcdata_tab MODE lv_mode .
IF sy-subrc = 0.
ENDIF.
*&      Form F_GET_DATEFORMAT
      This subroutine returns the date format in the user setttigs
     <--P_G_DATFM Date Format
FORM f_get_dateformat CHANGING p_g_datfm.                   "#EC *
SELECT SINGLE datfm FROM usr01 INTO p_g_datfm
WHERE bname = sy-uname.
ENDFORM.                    " F_GET_DATEFORMAT
*&      Form F_FORMAT_DATE
      This subroutine returns the date as per the user settings
     -->P_G_DATFM Date Format
     -->P_G_MM Month
     -->P_G_DD Day
     -->P_G_YYYY Year
     <--P_G_DATE Date
FORM f_format_date USING    p_g_datfm
                            p_g_mm
                            p_g_dd
                            p_g_yyyy
                   CHANGING p_g_date.                       "#EC *
CONSTANTS: c_dot VALUE '.',
             c_slash VALUE '/',
             c_dash VALUE '-',
             c_1 VALUE '1',
             c_2 VALUE '2',
             c_3 VALUE '3',
             c_4 VALUE '4',
             c_5 VALUE '5',
             c_6 VALUE '6'.
DATA: l_day(2),
        l_month(2).
l_day = p_g_dd.
l_month = p_g_mm.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
    EXPORTING
      input = l_month
    IMPORTING
      output = l_month.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
    EXPORTING
      input = l_day
    IMPORTING
      output = l_day.
CASE p_g_datfm.
    WHEN c_1.
      CONCATENATE l_day l_month p_g_yyyy INTO p_g_date
          SEPARATED BY c_dot.
    WHEN c_2.
      CONCATENATE l_month l_day p_g_yyyy INTO p_g_date
       SEPARATED BY c_slash.
    WHEN c_3.
      CONCATENATE l_month l_day p_g_yyyy INTO p_g_date
          SEPARATED BY c_dash.
    WHEN c_4.
      CONCATENATE p_g_yyyy l_month l_day INTO p_g_date
          SEPARATED BY c_dot.
    WHEN c_5.
      CONCATENATE p_g_yyyy l_month l_day INTO p_g_date
          SEPARATED BY c_slash.
    WHEN c_6.
      CONCATENATE p_g_yyyy l_month l_day INTO p_g_date
          SEPARATED BY c_dash.
ENDCASE.
ENDFORM.                    " F_FORMAT_DATE
thanks
bobby

Based On E-Mail Sales order automatically Created

Hi,
Customer will send the Email to Client for his / Her Sales Order (PO Order from Customer Side ) once client will get the Email from customer side, system will generate the popup Menu in that system has to show Details what customer wants with Accept for Sale order, check before Sales order confirmation ( Details ) & Reject
Once Accept the sales order system will automatically create a sales order and in that same customer mail system will send the Sales order confirmation O/P
Is it possible to Map into SAP?
If yes Please Guide me How to Map into SAP
Regards,
Prasanna

Hi,
You may configure an Inbound Idoc with sales order details like customer, material, quantity and expected delivery date, etc.
Since it is a third party system, you will have to map the fields and determine how it will be populated.
After that you may create sales order using BAPI_SALESORDER_CREATEFROMDATA or BAPI_SALESORDER_CREATEFROMDAT1.
Regards,
Amit

In VA01, how to automatically create a PO from a Sales Order

In VA01, I create a sales order using item.cat. TAS; then, system generates a PR for the sales order.
Is it possible to make the system create PO instead of PR?
In item.cat. configuration, I tried to check the check box "Create PO Automatic."; however, the system still geerates a PR for me w/o generating any PO.
Any idea would be appreciated.

Hi Vitthavat
In VOV6 for schedule line category CS check wheather the following data has been maintained or not
Order Type: NB
Item Category: X
Account assignment cat: 1
In VOV7 , for item category TAS
Check the box - Automatic PO generation
Billing Relevance - F
In MM02 , in Purchasing tab , check the automatic purchasing tab
Use ME59N for Automatic PO creation
Regards
Srinath

Create delivery automatically when sales order is created but not invoice??

Hi,
I have a requirement where in, it should create delivery (also issue) automatically when i create sales order, but it should not create the invoice automatically. I am going to do the invoice manually from the delivery document. Can you suggest me how to do this??
Thanks
Ghanesh

Hi,
If the sales document type is not relavant for Cash sale and the document type is used globally in the business then if for some specific conditions like distribution channel or plant or for division if u want to carry out the immediate delivery creation and PGI, use the below user exits and Bapi's
The below user exit is used to export the sales order details to capture the required checking cond such as sal org,dist ch,div,plant,etc
Include MV45AFZZ
FORM USEREXIT_SAVE_DOCUMENT.
Include MV45AFZA
FORM -USEREXIT_REFRESH_DOCUMENT.
BAPI_ISAORDER_GETDETAILEDLIST
BAPI_OUTB_DELIVERY_CREATE_SLS
SD_DELIVERY_UPDATE_PICKING
BAPI_OUB_DELIVERY_CONFIRM_DEC
Regards,
Gopal.

How To Automatically Create Planned Orders When Sales Order Is Saved

I have a MTO sceanrio where we need to create planned orders when sales orders are saved without running MRP.
I have the Planning Strategy Group set to 81 in the material master, but it didnt create the planned orders.
Could you tell me other settings I should review to make the planned orders create automatically?

Tony,
At the "Requir. Classes" (OVZG) customizing screen, field "Automatic start of make-to-order in background mode" affects the automatic planning. See fields help doc. below.
    If you select this indicator, the system automatically carries out
    single-item, multi-level planning for a sales order if a sales order
    item is either created or changed.
    This function can only be used for make-to-order production.
So check out the Req. Cl that yr Req. type (req. type is part of a strategy).
BR,
Elly

ATP Tree Structure is not getting created automatically after Sales Order is saved

In one one of our scenario, when we add material to Sales Order and save with Requirement Type(under Procurrement Tab of Sales Order) , in APO there is no planned order or only planned order which is dynamically pegged created because the ATP Tree in APO is not being converted. There is no pegging relevant item create(e.g. Planned Order). When we are checking the persistent ATP Trees in APO (/SAPAPO/ATREE_DSP - ATP-Trees) we can see that they are not converted automatically. They are still there. If we do it manually via transaction (/SAPAPO/RRP_ATP2PPDS - Conversion ATP Tree Structures -> Production Planning) it works. Afterwards the Planned Order is available and fixed pegged.
Why is APO not converting the ATP tree automatically ?
I also checked the scheduling horizon for conversion of the ATP Tree and it is correct: Is there any relation with Check Mode setting under ATP tab in Material Master?

Hi Prasad ,
This enables you to debug the ATP tree . If you have created an entry here with your user name then it will not let ATP tree get converted into PP/DS orders automatically .
It's very surprising because all seems fine . Just cross check all the settings once with below .
The conversion time depends on the following horizons and dates:
· PP/DS Horizon
· Scheduling horizon for the conversion of ATP tree structures
· Requirements dates in the ATP tree structure
PP/DS immediately converts the ATP tree structure when the sales order is saved
· If the earliest requirements date for components is within the scheduling horizon or
· If the latest requirements date for finished products is within the PP/DS horizon
If none of these conditions are fulfilled when saving the sales order, the system saves the ATP tree structure in SAP APO. In this case you can only convert the ATP tree structure online or in the background when one of the conditions given above is fulfilled. Here, there is an offset for the horizons with which you can achieve an earlier conversion.
You maintain the scheduling horizon for the conversion of ATP tree structures in Customizing for Production Planning and Detailed Scheduling under Maintain Global Parameters and Defaults. You maintain a location product specific PP/DS horizon in the location product master. If no location product specific PP/DS horizon exists, the system uses the PP/DS horizon from the planning version. You maintain these in Model and Planning Version Management.
Love Singh

Create purchase order automatically from Sales order.

Hi,
I have ticked Create purchase order automatically check box in item category TAS and TAB but still not able to generate Purchase Order automatically.???
any clue.
thanks/ashu

You need to have your prerequisites in place for the automated creation of the purchase requisition before the purchase order can be raised:
You may already have done this, but check that your material has the purchasing information on it (trxn MM02, purchasing tab), that a purchasing information record exists for that material and vendor in that purchasing org (trxn ME12), check that a source list exists as well (trxn ME02). If you have created the source list or purchasing info record after the sales order has been created then you will need to go into trxn ME56 to assign them manually. That should release the PO to be created.
In standard 3rd party, the PO is created using ME59 (prog RM06BB20), which can be run as a batch job.
Jon

Can't get my 3rd Party Sales Order to create the PO automatically...

I'm trying to get the 3rd Party Sales Order process to work and I would like it to create the PO automatically (it is already creating the requisition without issue). I have:
i) Set the Auto PO on the Item Category
ii) Set the ALE paramenters asociated with the Sales Org definition
iii) Set the Auto PO on the Vendor Master
iv) Set the Auto PO flag on the Purchasing tab of my NLAG material
v) Created a Vendor Info record
BUT I still don't get a PO being created automatically .... can anyone see where the problem may be?
Thanks.

Hi Dennis - I really appreciate the feedback but I started this thread with ....
I'm trying to get the 3rd Party Sales Order process to work and I would like it to create the PO automatically (it is already creating the requisition without issue). I have:
i) Set the Auto PO on the Item Category
ii) Set the ALE paramenters asociated with the Sales Org definition
iii) Set the Auto PO on the Vendor Master
iv) Set the Auto PO flag on the Purchasing tab of my NLAG material
v) Created a Vendor Info record
BUT I still don't get a PO being created automatically .... can anyone see where the problem may be?
I have since confirmed that I can trigger a PO creation by running ME59N BUT the PO is not created automatically when I save the sales order despite what the help text on the item category implies.
I think I have already done every you have suggested and even a little more, or maybe I'm missing something? Do I need to do something with ALE - turn something on perhaps? Have you actiually seen this functionality working? I'd love to hear from someone who has.
Regards.
Patrick

How to create sales order Automatically with reference to contract?

how to create sales order automatically through batch or online? can anyone please suggest what needs to be change in SAPMV45A program?

Hi,
Wt am able to understand from the above question is, you want to create automatic sales order against contract on a day to day basis by doing batch program, hope am wright.
See you can do it in two ways.
1. By using BDC, in SHDB T code record how exactly you will do transaction and then give it to your abaper rest he will do. he will write a program and he will schedule that program every day night.
2. By using BAPI. Just check in there are many threads are there which gives sales order bapi. Tell your abaper to map that bapi and tell them to schedule back ground job.
Hope this will help out in solving your problem.
Regards,
Nagesh

Relation btwn Sales order creation and automatically created Purchase Requi

Hello Experts,
The Purchase requisation is creating from Sales order, meaning, as soon as Sales order is SAVEing (say, SO_1), automatically a Purchase requisation (say, PR_1) will be created in the system. There is a Indicator filed in (PR) EBAN table, if its V, then this PR has been created from a Sales order. But, pls. let me know that,
How I can know that PR_1 is created from SO_1? meaning, I want to know the link btwn these 2 corresponding docs! I hv seen VBFA table, but, did not find any!!
thank you

Hi,
There is table called VBEP where U find Both fields
i.e VBEP- VBELN sales order number &
VBEP-BANFN Purchase requsition number.
Regards,
Sachin

Sales order to automatically create assembly order

Similar Messages

Maybe you are looking for