Converting SNP Planned Order /Purch Req to Prod.Order/Purch.Order

Guys
What is the standard process to Convert the SNP Planned Order /Purch Req. into a Prod.Order/Purch.Order ?
Can the conversion indicator be set in APO for SNP Planned Order /Purch Req.and then transferred to R3 as Prod.Order/Purch.Order or can the convesrion of Planned Order /Purch Req to Prod.Order/Purch.Order can be done in R3 itself ?
I am not clear on how exactly this works. Would appreicate if you could provide me with the standard process and any config involved in the same such as Number Ranges and how to set the conversion indicator automatically through SNP planning runs ?
Thanks

When you set this indicator for a planned order or a purchase
requisition, the system automatically converts the order into a
Production order or purchase order after the transfer to the
connected SAP R/3 system.
The converted orders are then retransferred to the SAP APO system with a
different category; a purchase requisition with category BS-ANF becomes
a purchase order delivery schedule line with category BS-EIN.
Please check configuration setting in SPro for transfer setting to R/3.
1. Configure Transfer to OLTP Systems(SNP)
2.Maintain Global Parameters and Defaults(PPDS)
Also on R/3 side you can see it in MD04/MD07 collectively for a product . or individually on
MD13 : planned order
MB51n: PR
Manish

Similar Messages

Unable to convert SNP planned order to PP/DS planned order in RRP3

Hi,
This is an in-house production scenario. SNP planned order are created based on forecast, now i want to convert those SNP planned orders to PP/DS planned orders in product view. While converting i am getting the following error message.
Conversion canceled with error
Message no. /SAPAPO/RRP707
I have checked the SNP, PP/DS PDS, it looks good.
Regards,
LV

Hi Lingaiah,
Conversion SNP -> PP/DS SAP002 is scheduling heuristic
Heuristic for Conversion SNP->PP/DS as SAP_SNP_SNGL used for order conversion.
Regards,
R.Brahmankar

Automatic mass conversion of SNP planned orders to Process orders

Hello,
we currently convert our process orders from APO by following steps:
1. In RRP4 - select convert SNP orders.
2. Click Save.
3. Set conversion indicator.
4. Click Save.
This is a very tedious tasks and we would like to automate this.
Reading previous posts - I know this can somehow be achieved in transaction RRP7. However, I haven't been able to convert SNP orders (steps 1. and 2.) in RRP7 yet. Does mass conversion only apply in setting the conversion indicator?
Best Regards,
Sam

Hello,
thanks for your reply.
We are currently processing orders in RRP4. We would like to automate this process as much as possible that is why we are considering RRP7. However, I haven't found a way to automatically convert SNP planned orders to PP orders in APO.
Best Regards,
Sam

Order type selection when converting from planned order to prod order

Hello friends,
I have one doubt.That when i am converting the planned order to the production order than from which default settings it takes the order type.
As we can maintain the default order type in OPPQ , under conversion and in production scheduling profile also we maintain order type for make to stock, make to order, etc.
So my question is to which setting the system gives the priority.
Or they both are for different purpose.
Thanking you guys in advance.

Hi ,
You can maintain the order type for conversion of planned order to production order in the T Code OPPE.
Hope it will be clear.
Regards,

SNP Planned Orders to ECC Process Orders - no PPDS

Hello Gurus,
Is there a way to covert an SNP Planned orders to ECC Prod. orders? Can one switch off the PPDS in APO and still get the MRP/ MPS planning in APO and and convert those SNP planned orders into ECC orders in ECC
Thanks.

Hi Abhi,
When you CIF SNP and PPDS planned orders to ECC system there is no diffrenciation between both of them (Because component specific details for the orders are not captured in ECC). So in ECC system you can convert Planned orders to Process or production orders by switching PPDS off in APO.
In APO system, SNP itself can plan for all the levels (RM,PM,FG,SFG) so no need of doing MRP.So you can switch off PPDS.
MPS functionality is available in ECC and not in APO system.
Thanks and regards
Sravan maturu

Deployment of SNP Planned orders

Dear Expert,
We have one scenario where there is a requirement to deploy SNP Planned orders. How much it is advisable to deploy SNP Planned orders?
What will be the impact on the dates of shipment proposals made by TLB, when SNP Planned order will get converted in Planned order and production order.
Also I observed one strange behaviour of deployment, when I try to deploy planned order by putting ATD receipts as planned order in SNP2 tab, some times it considers the planned order for deployment but many time it doesn't.
Is there any specific settings other than ATD reciepts in SNP2 tab of product location master data?
Thanks & Regards

Dear Samuel/Amol,
Thanks for your reply. Let me frame this question again
Letu2019s consider that I have maintained SNP planned orders in ATD Receipts. After running deployment, system will look for SNP Planned order as receipt element in Pull deployment horizon and create DepConRel . TLB only considers DepConRel for conversion into STO, irrespective of stock is available or not.
Now consider the situation where STO is ready with some specific Delivery & committed dates but there is no stock. When SNP Planned order will get converted into planned order and Production order, its date will change and actual stock may not be ready on that specific committed date.
So my entire intension is to know how much it is advisable to deploy SNP Planned order.
Samuel/Amol, did you get a chance to work on SNP Planned order deployment and its impact on the dates of STO?
Thanks & Regards,
Chetan

How to Change Component on a SNP Planned Order ( Just 1 time )

Hello,
We are trying to change a component on a SNP Planned Order just 1 time.
So we do not want to change the PDS since this is one time change only.
We tried changing it in R/3. Once we do that, R/3 shows new component but APO still shows dependant demand on old component ( May be because APO SNP Planned order is still connected with the PDS ) .
Then we went to APO and tried to change the component in /sapapo/rrp3. Here you can delete the old component but doesn't let me add new component.
Next thing we tried was to convert it to PPDS Order. Once converted, we went to change mode and tried to remove old component and add new component. It lets me do this. Only issue with this route is that, it puts correct start and end dates on the order dependning on the order quantity and so order moves the dates which we do not like.
Is there any other better way to fix this issue ?.
Thanks.
Ketan Doshi.

This being a very unique requirement, I would use one-off approaches usually not followed. You may need to explore the use of BAPI BAPI_MOSRVAPS_CREATESNPORDER. This will help you point the source of planned order to a PPM or a PDS that you may want to create in APO system on a one-off basis. PPMs can be maintained in APO, however PDS are usually CIFed from R3. You can try to create PDS (based on the new component) in APO system only using backend tables. Try do some little research on /sapapo/curto tables to create the PDS in APO. Then use the BAPI to point the source to this new PDS. (better you also try the PPM approach since there are no issues keeping the PPM in APO)

SNP planned order deleted in APO, but not in R/3.

OK Guru's,
We have a situation where during the weekend SNP planning runs, SNP Planned orders are deleted in APO, but the order is never deleted in R/3. The change pointer is not in CPP and there are no failed queues. Also, when you run CCR on planned orders, we will get an error on some orders saying "Not in APO" and the only option to reconcile that order is to "Send to APO". The option that should exist is "delete in R/3" becuase the deletion never occured in R/3.
If you send the order back to APO, the order will show in the "Production Confirmed" line of the Planning Book. This is because APO is thinking that this order is an order that was created in R/3 when in fact is it really is a SNP planned order.
Any clues to why this would happen?
thanks,
Brian

How are you getting the SNP Planned Orders to R/3 in the first place.
If you are transferring them using /SAPAPO/RRP7 then I guesss its a manual transfer and system does not consider SNP Planned Order deletion flag relevant for transfer to R/3.
You will need to look into CIF enhancement to send the deletions to R/3.
Normally SNP Planned Orders are not relevant for transfer to R/3 unless its replaced or converted to a PPDS planned order.
Somnath

Default PR Type when convert from Planned Order

Hi all,
How can I default my PR Type when convert from Planned Order after MRP run. This can done via MRP Group control but how to go about controlling via Planned Order profile?
Which planned object type and planned order profile to be used? assuming that i need my planned to be output at LA type and convert to NB1 PR type instead of the default NB PR type?
Thanks.
Regards,
Andrew

Hi,
The system determines the document type from the stettings u are making in "planned order Profile" in Customising for MRP. There u define the order type, the procurement key and the special procurement key and also the account assignment category. So based on the procurement key and the special procurement key maintained in the Marterial master, the document type is selected.
Production > Materials Requirement Planning > Procurement Proposals > Planned Order > Define order profile
Choose the planned order type - NB1 Within this you specify the P req doc type to be used.
Through MRP group and the different PR document type for MRP generated PR is possible only if you assign the document type to MRP group in the MRP configuration.
Please try and come back.
Regards,
R.Brahmankar
Edited by: R Brahmankar on Aug 28, 2008 10:54 AM

Convert SNP Orders to PPDS Orders in CIF

We have a requirement to segregate the orders created in SNP and scheduled in ECC. I know this can be done with the Production Planned and Production Confirmed key figures based on ATP Category as EE is for SNP and AJ, AK, AL, AI are PPDS. The complication is we are not using PPDS for short term scheduling; therefore ECC will control the short term scheduling. We are currently removing the Firm indicator on ECC for any SNP (EE) order using a user exit. This allows for seeing the SNP orders as not scheduled (not firmed) in ECC. When the scheduler firms the planned order in ECC we want the order to show in the production confirmed key figure in SNP. This can be done by setting the EE Firmed to the Production Confirmed key figure, but now the SNP Planner has SNP Orders on two different key figures. Therefore, our requirement is to change any SNP order (EE Category) to a PPDS order if it is firmed. This way Production Planned are SNP orders only and Production Confirmed are scheduled or created ECC orders.
We have tried using APOCF004 to change the APOAPPL from a 3 to a 1 and BADI ORDER_INB_MODIFY_AFTER_MERGE changing cs_ordkey-appli from 4 to 2. Neither of these options worked. Possibly because of the difference in structures and number range, the system is not doing the convert.
Thank you in advance for any suggestions.

Hi,
Please check the settings in the heuristics SAP_SNP_SNGL(Individual Conversion SNP --> PP/DS) or SAP_SNP_MULT, whatever you are using.
PPDS horizon is relevent for the conversion and SNP horizon may not be relevant.
The details are as below:
The conversion horizon for SNP to PPDS is decided as below.
Conversion Hprizon
The offset and the PP/DS horizon together define the conversion horizon, that is, the period in which you want to convert Supply Network Planning (SNP) orders and Capable-To-Match Planning (CTM) orders into Production Planning and Detailed Scheduling (PP/DS) orders:
Conversion horizon = PP/DS horizon + offset
You must specify a positive value for the offset. The conversion horizon begins on today's date and continues for the relevant number of calendar days into the future. So that the system converts an SNP or CTM order into a PP/DS order, the start date/time of the order must be within the conversion horizon. If you want to extend the conversion horizon to the end of the SNP or CTM planning period in which the end of the conversion horizon lies, you enter a daily buckets profile.
Hope this helps.
Regards
Datta

Process orders not reflecting in SNP planning book

Hi,
I am facing a problem here that the SNP planned orders once converted into process orders in ECC are not reflecting in the SNP planning book.
However if i check the /sapapo/rrp3 product view, the process orders are visible here.
Kindly help me understand if i am missing out something here.
Thanks,
Nalin

Hi,
Please Check whether the ATP category is assigned to the Category group which is assigned to KF in the planning.
If that is assigned rightly then run TS cons check.
Regards,
Kishore Reddy.

Difference between snp planned order and pp/ds planned order

Hi to all,
can any one please explain the difference between snp planned order and pp/ds planned order. I am relatively new to this area

The primary differences are as below.
1. The master data for SNP Planned Order is SNP PPM/PDS where the minimum duration for an operation is a day. So it is used for rough cut capacity planning.
The master data for PPDS Planned Order is a PPDS PPM/PDS where operations are down to minute and second level. Moreover sequence dependent operation planning is possible in PPDS Planned Orders. It is for detailed capacity planning.
2. SNP Planned Orders are created in SNP while PPDS Planned Orders are created in PPDS or when transferred from ERP to APO.
3. SNP Planned Order need to be converted to a PPDS Planned Order before it can be used in the Execution System (ERP) for further processing - like conversion to Production Order. Moreover the category types of the orders are different in APO (EE for SNP and AI for PPDS).
Hope this helps.
Somnath

Creation of SNP planned order based on PDS

Hi,
I'm a APO developer and I have the following problem:
I would like to create a SNP planned order based on a PDS (like e. g. in the planning book when you input a number into a cell in the "Production (Planned)" line).
Up to now I've only managed to create such an order without using the PDS.
Can you name me a function module which allowes me to do that?
Thanks in advance.

Hi,
I've now managed to create this kind of order.
I set a breakpoint at the function module /SAPAPO/DM_PROD_ORDER_CHANGE and checked how it was filled in the planning book.
For those who want to know:
INCLUDE /sapapo/constants_om.
CONSTANTS:
    lc_order_type_1f        TYPE /sapapo/om_order_type VALUE '1F'.
DATA:
    ls_prod               TYPE /sapapo/msnp_prod,
    lt_prod               TYPE /sapapo/msnp_prod_tab,
    ls_sources            TYPE /sapapo/sources,
    lt_sources            TYPE /sapapo/sources_tab,
    lv_matid              TYPE /sapapo/matid,
    lv_locid              TYPE /sapapo/locid,
    lv_vrsioid            TYPE /sapapo/vrsioid,
    lv_tstfr              TYPE /sapapo/timestamp,
    lv_tstto              TYPE /sapapo/timestamp,
    lv_simsession         TYPE /sapapo/om_simsession.
lv_vrsioid = '000'.
* Create SimSession
CALL FUNCTION '/SAPAPO/TSIM_SIMULATION_CONTRL'
    EXPORTING
      iv_simversion              = lv_vrsioid
      iv_simsession             = lv_simsession
      iv_simsession_method = 'N'
      iv_perform_commit       = space
    EXCEPTIONS
      lc_connect_failed        = 1
      lc_com_error             = 2
      lc_appl_error            = 3
      multi_tasim_registration = 4.
IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
* Get PDS
CALL FUNCTION '/SAPAPO/MSDP_SNP_PPM_VALIDITY'
    EXPORTING
      iv_vrsioid      = lv_vrsioid
      iv_matid        = lv_matid
      iv_locid        = lv_locid
      iv_tstfr        = lv_tstfr
      iv_tstto        = lv_tstto
      iv_planstart    = lv_tstfr
      iv_planend      = lv_tstto
    CHANGING
      ct_sources      = lt_sources
    EXCEPTIONS
      wrong_interface = 1
      error_occured   = 2
      OTHERS          = 3.
IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
READ TABLE lt_sources INTO ls_sources INDEX 1.
ls_prod-version       = lv_vrsioid.
ls_prod-matid         = lv_matid.
ls_prod-locid         = lv_locid.
ls_prod-plobid        = '9AMALO'.
ls_prod-tstmp         = lv_tstfr.
ls_prod-catgr         = 'PP1'.
ls_prod-categ         = 'EE'.
ls_prod-categ_prku    = 'EE'.
ls_prod-categ_prse    = 'EL'.
ls_prod-kz_prod       = '9APPROD'.
ls_prod-kz_prku       = '9APPROD'.
ls_prod-kz_prse       = '9ADMDSE'.
ls_prod-produ         = '1000'.
ls_prod-proid         = ls_sources-trpid.
ls_prod-mosta         = gc_new.
ls_prod-order_type    = lc_order_type_1f.
ls_prod-is_fixed      = 'X'.
ls_prod-snp_is_header = 'X'.
APPEND ls_prod TO lt_prod.
CALL FUNCTION '/SAPAPO/DM_PROD_ORDER_CHANGE'
    EXPORTING
      ic_database           = 'LC'
      ic_application        = '4'
      iv_simsession         = lv_simsession
      it_prod               = lt_prod
      iv_netch              = 'X'
    EXCEPTIONS
      material_not_supplied = 1
      location_not_supplied = 2
      OTHERS                = 3.
* Merge simulation version (to commit order changes)
CALL FUNCTION '/SAPAPO/TSIM_SIMULATION_CONTRL'
    EXPORTING
      iv_simversion                = lv_vrsioid
      iv_simsession                = lv_simsession
      iv_simsession_method         = 'M'
    EXCEPTIONS
      lc_connect_failed            = 1
      lc_com_error                 = 2
      lc_appl_error                = 3
      multi_tasim_registration     = 4
      target_deleted_saveas_failed = 5
      OTHERS                       = 6.
IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.

Bapi for sfg dependent dem,snp planned order qty, and ppds planned orde qty

Hi Gurus,
I am not much familiar with APO, so please help me,
Input details:
Field                         Value
Planning Version     000
Source Location *     1001     Single/Multi Value
Product *                          1000061     Single/Multi Value
Production Planner *     PRC     Single/Multi Value
Start Date *
End Date *
o/p:
Source Location     Date     Semi-Finished Material     Material Description     SFG Dependent Demand     SNP Planned Orders qty     PPDS Planned order Qty     Total SFG Variance due to Lot size     Total SFG Variance reference to dependent demand
1001     15-Jul-10     1000041PP     PRIMARY FF MILK 3% FAT     340     412     420     8     80
1001     15-Jul-10     1000041PP     PRIMARY FF MILK 3% FAT
1001     15-Jul-10     1000041PP     PRIMARY FF MILK 3% FAT
Is there any bapi to fetch the data as shown in o/p.
Thanks

Hi Phani,
Tryout the below BAPIs
IF10503 (object)
BUS10503
Regards
R. Senthil Mareeswaran.

To build query related to SNP: Planned Order

Hi,
System: SCM 5.0
Scenario: SO received at plant and planning creates PR against SO at plant and accordingly SNP:Planned Order at Vendor location. If SO is cancelled/deleted (manually), sometime only the PR gets cancelled/deleted (automatically during planning run) but corresponding SNP:Planned Orders still remains at vendor location and so the dependent requirements. PR and Planned Orders are pegged to SO so one-to-one relation is maintained.
I could not find any reason why system is not deleting Planned Order at vendor location despite SO and PR is deleted at plant location. So I am planning to build query where SNP:Planned Orders are not pegged to any PR or SO.
Can anyone help with list of SNP:Planned Order tables so that I can build query around it to identify ghost Planned Orders.
Hope I was clear with my query but let me know if any further information is require.
Thanks and regards,
Devang

HI Marius,
Sorry for delay reply.
I was working on on some other more critical issues to business.
Finally we decided to built report to identify obsolete Planned Orders for which PR is not available in ordering plant. I have listed below logic for that report:
Get Location ID from table /SAPAPO/LOC based on Location entered in selection screen
Get PEGIDs from FM /SAPAPO/DM_MATLOC_GET_PEGIDS based on IV_SIMID as 000 and location id from step 1
In FM /SAPAPO/OM_PEG_CAT_GET_ORDERS, use SIMVERSION as 000 and in Import Para IS_GEN_PARAMS insert all PEGIDs from step 2.
From Export Para ET_PEG_INPNODE take From_OrderID and store in internal table.
Execute T.Code /SAPAPO/RRP4 with following selection (Use Selection Variant: OBSOLETE PR and add Location as entered in Selection Screen)
Planning Version: 000
From: Current date – 60 days
To: Current date +180 days
Location: 0000201328
Product: *
Order Type: 1F
6. Compare output of step 4 and step 5 and display result.
From FM /SAPAPO/DM_MATLOC_GET_PEGIDS the output (step 4) will be Order ID (22 characters) while step 5 (T.Code /SAPAPO/RRP4) will give Planned Order number (8 character). I am not sure how to compare Internal Order ID (22 characters) for corresponding Planned Order Nos. (8 characters).
I have not marked your post as correct answer as still need to find answer of above query.
Thank you in advance for your guidance.
Regards,
Devang Shah

Converting SNP Planned Order /Purch Req to Prod.Order/Purch.Order

Similar Messages

Maybe you are looking for