Deletion and creation of SNP Planned order

Hi,
I need to delete the SNP Planned order i.e ATP category of type 'EE' and I have to create the orders of ATP category EE through programetically. Please let me know if any BAPI's or Function modules are existed for the same.
Appriciate your help.
Regards,
Ratna

Hi Ratna.
To delete orders in SNP use transaction:
/SAPAPO/RLCDEL
BAPI to create planned orders:
BAPI_MOSRVAPS_SAVEMULTI3
There is also a BAPI to delete planned orders if this is more suitable.
BAPI_MOSRVAPS_DELEMULTI
Hope this helps, M

Similar Messages

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.

Creation of SNP Planned Orders using Optimizer

Dear Experts .....
I am facing some problems while creating SNP Planned orders using Optmizer ( Discret Optimization).....
For eg.
I am using 3 months horizon ... the first two months is daily buckets with 12 hours capacity each one and the last month is weekly buckets.
The product minimun lot size exceed the daily capacity .... this way planned order have been created in the weekly buckets at the end of the horizon.
I need the system to create orders in the correct date avoiding use of safety stock .....
Regards
Mauricio

Those other 2 settings was already done .....
It is still not working .... iI am receiving the following message ...
Production process model/PDS 00000000000001011301001 S: Cannot be executed
Message no. /SAPAPO/SNPOPT159
Diagnosis
Production process model 00000000000001011301001 S at location 0100 is intended for cross-period lot size planning. It can be started in bucket 20110404->20110404. However, it does not then end in the same bucket.
Thanks for your effort trying to help me with this issue.

Creation of SNP planned order in Monthly Bucket though CTM plan

Hi,
Can anyone advise how to aggregate the SNP planned order generated after CTM run in Monthly bucket.
Can it be done through customizing?
Regards.
Punit

system switches over to external procurement in place of in house production only when you use optimizer.
Heuristic will do this only if there is a SNP PPM/PDS and the resource calendar prevents timely production.
Regards
Nitin Thatte

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

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

Delete SNP Planned Order to reflect at R3 (C5 or CCR)

Hi,
I deleted some SNP planned order using rlcdel, should i use a C5 or CCR to transfer to deletion toR3 to reflect the changes . ? what situation should i used C5 or CC5
many thanks

Hi,
RLCDELETE has the radio buttons "In APO" and "In APO and R/3". if you check the "In APO and R/3", the deletion is immediately sent to R/3. No need to run C5. If not then you just deleted the order only in APO and did not delete in R/3. You can either run C5 and select the change pointer with "R"- delete or run CCR report or delete these orders manually in MD16 in R/3.
what situation should i used C5 or CC5
C5: When you sent periodic transfer in SPRO, then create an order and push it to R/3. You can also delete an order and push the delete change pointer (R) to R/3
CCR: When the orders in APO and R/3 donot match.

SNP Planned order start and end dates are not calculated correctly

Hello SNP Guru's
The SNP planned orders generated after the Heuristics run, have a start and end date based on the Activity Duration (Fixed), while the resource consumption is based on the Bucket Consumption (Variable), which is correct.
The Activity Duration (Fixed) is based on the BOM Base Quantity. So if the Activity Duration = 1 day, and if the order quantity is more than a day, the start and end dates, still shows as 1 day. So no matter what is the order quantity, the start and end dates is always = 1 day.
Does anyone have any experience in implementing any code to change the start and end dates on SNP Planned Order?
Seems like it should work as standard.
Am i missing something?
Thanks,
Mangesh

Dear Mangesh,
SNP is a infinite planning tool. If you have defined fixed duration to be 1 DAY in the activity, no matter how many quantity you input for your planned order, the order will last for one day. If the resourced is overloaded, you then run capacity levelling to
banlance the capacity. What your expected beahavior happens in PPDS planning.
Claire

SNP planned order availability date difference between APO and ECC

Hi,
I have observed that SNP Planned order availability date is not matching between APO and ECC. Details are as follows.
I ran SNP Optimizer with bucket offset of 0.5. After publishing the optimizer created planned orders to ECC, only start date is matching.
Example:
I am using PDS as a source of supply.
Fixed production activity in SNP PDS is 1 day.
GR processing time: 3 day
After running optimizer planned order is created with dates explained below.
Start date/time: 09.05.2011 00:00:00
End date/time: 12.05.2011 23:59:59
Availability date: 16.05.2011 00:00:00
Because of bucket offset defined as 0.5 optimizer planned order availability is start of next monday.
After publishing this planned order to ECC dates on the planned order is as follows.
Start date: 09.05.2011
End date: 09.05.2011
Availability date: 12.05.2011
I have not maintained any scheduling margin key in ECC. Also if I dont define the GR processing time, planned dates between APO and ECC always match. Can anyone explain the impact of GR time on the availability date.
Regards,
Venkat

Hi Venkadesh,
What's "state stamp"? Do you mean different time zone?
note : 645597 mentioned by Nandha is very helpful:
In standard, CCR will use duedate - "the available date of the output product".
Nandha's words "In SAP APO, if the receipt date of the primary product deviates from the
end date of the last activity of the order, the receipt date
always identifies this as inconsistent. You cannot rectify
inconsistencies of this type by using CCR."
I guess in your PDS or PPM, the output product is not assigned to the End of the last activity. Someone changed it?
Please CIF the PDS or PPM again.
If you really want to apply a note, please use note 815509 as you're using planned order,
and system will use order end date in CCR instead.
GR time is always considered. BR/Tiemin

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

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.

SNP Planned order - Doesnt get the complete BOM when CIFd to ECC

Hello,
When we create SNP Planned order in APO and sent to ECC, the Planned order doesn’t get the complete BOM, it works for the most part, except if we have Materials from multiple plants within the same BOM (sourcing from multiple plants).
Do we have to do any separate Configuration for this scenario?
We are planning only the End item in SNP, and we are generating the production version and PDS transfer to APO. We are not transferring all the materials to APO.
if we go to the Change mode of the Planned order in ECC and re-explode the BOM, I get all the components from the BOM, its just that when the planned order gets created thru the CIF we have this issue.
Any help would be appreciated.
Regards
Gk

Hello Marius
Thank you for your quick response.
I looked at the SAP note you mentioned, the description seems to be matching with the issue we are having. Recently we had SNC implemented, and the note states that that can be the case why the components are getting deleted during planned order creation.
The only thing about this note is its very old, and we are having the SAP 6.0 and SCM 7.2 ,
Do you think this would be still applicable.
I will look into the details and let you know whether the note is applicable for us.
Regards
Gk

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

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 not following resource bucket capacity/factory calendar

Hi gurus,
SCM 5.0
I am running SNP heuristics for a product and expecting planned orders for it. It has corresponding production data structure and multimixed resource. The resource has an assignd factory calendar and SNP bucket capacity. The bucket capactiy availablity dates of the resouce is consistent with the factory calendar workdays/holidays. Using simple lot for lot strategy, I am expecting heuristics to schedule the planned orders on the dates of the demand in compliance with teh SNP bucket capacity availability of the resource. APO does not schedule on holidays consistent with bucket capactiy. This is true until...
We have a public holiday in factory calendar that needs to become a workday. To remedy this, we put a special rule for the factory calendar and explicitly made that holiday into a workday. The changes were synchronized with APO, and this is also reflected in the bucket capacity of the resourc: former holiday now has bucket capacity after the calendar change. However, when running heuristics, it still does not create SNP planned order on that former holiday that has been changed into workday. Even if it is a public holiday, there is already a special rule for the factory calendar and the resource bucket capacity reflects this correctly. But SNP heuristics seems not to follow this change.
Any ideas on this? looks like a bug.

Hi Edgar,
Yes, when your resource reflects the addional capacity of the holiday turned working day, then it is expected to be considered for the SNP planned order.
Instead of SNP heuristics, you may try to check interactively in SNP planning book, if manual order creation in the bucket works out.
Since this is a mutlimix resource , it can also be checked if in PPDS planned order can be created on the day.
The above checking may not solve your problem , but will get to know if at least manully the bucket is being considered or not.
regards
Datta

Deletion and creation of SNP Planned order

Similar Messages

Maybe you are looking for