Block transfer of VP planned orders

Dear Experts
We need to exclude VP planned orders from APO during CIF transfer. We should have LA planned order and production orders ciffed. Which enhencement do you recommend.
Kr. Ann L

Hi,
check  customer Exits For Planned Orders and Manufacturing Orders in APO.
APOCF004 u2013Inbound processing of planned orders and manufacturing orders
Customer Exits For Planned Orders and/or Manufacturing Orders in R3.
CIFORD02 u2013 Enhancement for the transfer of customer-specific order fields (SAP R/3 u2192 SAP APO)
Thanks,
nandha

Similar Messages

  • Block the creation of planned order

    Dear experts
    How can I control the creation of planned order? I want to block the creation of planned order if the BOM or routing is not exist.
    BRs

    Hi,
    I think this can be done using 'Material status' try the following and let me know if it works.
    Create a new material status in transaction OMS4 (like R1 - "Created but BOM and Routing not maintained" )and in the details screen select Option "B" for MRP messages.
    You designate a material as a "R1 -Created but BOM and Routing not maintained" In the master record.
        MRP                          "B" = warning
    Please try this and let me know the result.   
    Regards,
    Prakash

  • CIF blocked .. due to planned order quantity too small

    Hi,
    we facing the issue of whenever planned order generated after optimizer run. if the quantity of planned order < 1 i.e 0.8pcs . It will get stuck and won't cif to R3... any solution for this ..??
    thx  in advanced
    regards

    Hi
    Can you please clarify the following:
    1. Your Base Unit of Measure.
    2. Any Min/Max Lot and rounding values maintained in ECC/APO.
    3. PPM/Prod Version Lot sizes defined.
    4. What is your BOM base quantity?
    Also please elaborate the issue with proper examples, for us to help you better.
    Regards,
    Manjit
    Edited by: Manjit Pahal on Aug 7, 2008 2:00 PM

  • Transfer LTP planned orders to Operational planned orders

    Hi
    Can anyone suggest how to transfer planned orders generated from LTP(Long Term Plan) to Operational Plan?
    Regards
    Pradipta Sahoo

    Dear Sahoo,
    You can transfer the simulative planned orders to operative planning using T Code MD43.
    Check this,
    Copying the Long-Term Planning Results to Operative Planning  
    Use
    Once you have optimized the results of long-term planning, you can copy them to operative planning.
    It is not only possible to copy the demand program to operative planning, you can also copy the planned orders firmed in long-term planning per material using the MRP transaction Interactive single-item planning.
    When copying the results to operative planning, you can set the system to create purchase requisitions and delivery schedules instead of planned orders for materials procured externally.
    Prerequisites
    You must firm the simulative planned orders you want to copy to operative planning. You can firm planned orders by:
    Making manual changes
    Using the planning time fence
    Setting a manual firming date
    If, when copying the data to operative planning, you want the system to create purchase requisitions or delivery schedules for materials procured externally instead of planned orders, enter the appropriate indicators in the Create pur. req. and Schedule lines on the initial screen of single-item, interactive planning (in MRP).
    When copying the results to operative planning, the system does not carry out any source determination. If you want the system to create delivery schedules and purchase requisitions to which a vendor has already been assigned, you must maintain the necessary master data in the Purchasing menu before carrying out the planning run in long-term planning.
    http://help.sap.com/saphelperp60_sp/helpdata/en/92/bf02af44bd11d182b40000e829fbfe/content.htm_
    Regards
    Mangalraj.S

  • Issue in Deployment of SNP Planned orders

    Hi Experts,
    I am trying to deploy SNP Planned orders and I have made relevant settings in SNP2 i.e. ATP category in ATD Receipt.
    When I run deployment, it creats deployment stock transfer (DEP: PReq / DEP:ConRl) based on available stock first. When I run deployment second time, then it creats deployment stock transfer( DEP: PReq / DEP:ConRl)  for SNP Planned order with the same quantity of stock & not for entire quantity of SNP Planned order. Please refer below example to make it clear
    Total Demand at destination location = 600
    Stock at supply location = 100
    After planning run, Purchase requsition of 600 is generated at destination location.
    At supply location, SNP Planned order of 500 is generated considering 100 stock is available against PReqRel of 600.
    When I run Deployment first time, it forms DEP: PReq / DEP:ConRl  of 100 based on available quantity of 100.
    After running Deployment second time it forms again DEP: PReq / DEP:ConRl  of 100 and it continues to create deployment stock transfer till it completes the quantity of SNP planned order.
    So all together it creates 6 deployment stock transfers instead of forming one deployment stock transfer (stock+ SNP Planned order).
    There is no lot size setting for product master.
    Can anyone suggest whether I need to do some settings to get one deployment order instead of 6.
    Thanks & Regards,
    Chetan
    Edited by: Chetan Patil on Nov 10, 2010 4:45 PM

    Hi Chetan,
    It looks the SNP planned order is not being considered in the receipts quantities  to be available for deploying against requirements.
    Please check SNP order  ATP type( it  is normally EE)  is included in the appropriate Categroy group
    IMG >> APO > Supply Chain Planning  > SNP > Basic Settings > Maintain Category Groups
    Example :  ATD Receipts:   ATR
    Typical values :    AI, AJ, BF, CC,EE,EF, EI
    Secondly, in the transaction /SAPAPO/MSDP_ADMIN, in the Key Figure detailed  tab, ATD Receipts should have assigned the Category Group(say  ATR).
    Regards
    Datta

  • SNP Planned Order without PPM

    Hi Gurus,
    I have a small confusion, Some of my products in a Production Plant donot have a  SNP PPM. and when i run network heuristic on that location product. It creates SNP Planned orders.
    Just for information the product location master has procurement type E (In House Production).
    Please help me out if this is a normal behavior of the system.
    Thanks,
    M

    Default behavior is to generate Orders without a source of supply.
    "If there is neither a valid transportation lane (for procurement type F; external procurement) nor valid PPM/PDS (for procurement type E; in-house production), the system creates an SNP stock transfer or SNP planned order with no reference to a source of supply. The same applies if there is no product at the source location of the transportation lane"
    if you dont want planned orders there,
    Try using the SDP relevance indicator for the location - product . Am not sure but you can use option 1 in it (though it sounds like it will not plan in DP too)

  • "CLOSED": HOW TO LOAD FIRM PLANNED ORDERS OF ANOTHER PLAN INTO ASCP PLAN?

    Hi everybody,
    How to load firm planned orders of plan 1 into plan 2?
    Business Case:
    Customer uses a separate planning for order intake. During order intake the requested due date is validated based on ASCP Gantt Chart. Bottlenecks are resolved. For make items firm discrete jobs are created, if adjusted suggested due dates are manually changed. For buy items firm planned orders are created for manually changed suggested due dates.
    If the order is accepted the demand is transferred from the Order Intake MDS into the so called Operational MDS. The firm discrete job will be automatically visible in the operational ASCP Plan (after data collection/running ASCP Plan).
    But how is it possible to include ONLY firm planned orders of another plan into your current plan?
    PLAN1 asigned master demand schedules
    - O_MDS1
    - O_MDS2
    PLAN2 assigned master demand schedules
    - O_MDS1
    - O_MDS2
    - T_MDS
    I want to transfer the firm planned orders from plan2 to plan1.
    Thanks for all your inputs,
    Catalina
    Message was edited by:
    user447176

    Since you need to run a data collection to load the new discrete job, I suggest you to add a custom step in the data collection.
    This custom step will
    1) select all firmed planned order in plan 2
    2) put the firm planned order into a new schedule through staging tables (MST_ST_SUPPLIES) .
    3) collect the data
    Then run plan1 with this schedule defined as demand schedule for your new plan.

  • Pls help - Urgent - Planned order transfer from APO to R/3 - inconsistency

    Hello experts ,
             Iam creating planned orders in APO using CTM planning. The planned order is getting transferred to R/3 but the order number is different in APO and R/3 .
             I tried deleting the application logs in R/3 and APO using transactions CFGD and C6 and running CTM planning again. But it did not work.
            Kindly suggest a solution. Thanks

    As other members adviced
    Please check the following as a list
    1) Check first fi the Material is in APO relevant
    2) Check if it has active integration model in cfm5 (R/3)
    3) Check if the material has no blocked queues in /n/sapapo/cq (APO)
    If there are any blocked queues please clear them accordingly.
    4) After that perform a reconciliation of the transactional data through.
    /n/sapapo/ccr(APO). perform it only for that material and on planned orders.
    If there are any errors it will usggest you to follow few steps.
    5) then again go back and check the /n/sapapo/cq transaction.
    6) Check if the material and its location has publication Types maintained in SPRO transaction.
    7) Check if the change pointers of this Planned order exists in /n/sapapo/c5
    This si change pointers transaction , soemtimes you can release ti from there also.
    If you still have problem, give the resutls of the following for reference.
    Let us know once you perform all these.
    8) Incase you need to perform the consistency checks  externally.

  • Block Plan Order and Purchase Requisition in Sales order creation.

    Please tell me, how to block Plan Order and Purchase Requisition while creating Sales Order. When we create a sales order, plan order and purchase requisitions are also created by their own, please tell me, how can we block them while creating sales order. Please do let me know as soon as possible.

    hi,
    generally thy wil not be created automatically.
    may be som configuration or exit is used in ur system.
    check in debugging mode while saving ur salesorder.

  • How to block planned order when there is a credit block in sales order

    Hi Experts,
    Planned order should not be created when there is a credit block at sales order level. Can someone help me in solving this?
    Expecting for your valuable comments.
    Regards,
    JANA

    Go to t.code OVB8 and add routine 101 under routine column and routine 1 under system routine column and then create new document and test.
    Regards,

  • Planned order CIF blocks

    Hi,
           This is continuation of my previous [post|No IModel active for cat. Planned Orders]
    I am getting the CIF blocks starting with CFIP00... and these are from the program,/SAPAPO/RDMCPPROCESS, that collects and pushes the orders to R/3.
    Now the strange thing is I get about 200 of them every day and when I delete the first CIF block, all the queues will be deleted immediately. This is probably the 5 or 6 time in a row. Every time I run this program, I get the blocks. After deleting the first queue, everything else gets cleared immediately.
    I checked in the active integration model the material at that plant is in there.X0 maintained,  and the planned order in that first queue is not the same material every time!
    Any bod has any suggestions?
    Thanks.

    Hi Manish,
                       I activated the first one and it said running and came back to the same error SYSFAIL.
    I checked SLG1, it's the program /SAPAPO/RDMCPPROCESS that was runs at 02:10 AM and that's almost the same time in CIF
    queue as well.
    I checked SLG1 and there is a log with grey icon (instead of green or red) with
    object text:Core Interface Application Log Object and
    Subobject text: In-House Production (Inbound)
    Program: /SAPAPO/SAPLCIF_GEN
    Mode: Batch processing
    When I double click, I see no message but when I select the log and click on spectacles icon, here is the text:
    ===
    Identification
    Object________________ CIF (Core Interface Application Log Object)
    Subobject_____________ IP (In-House Production (Inbound))
    External ID___________ IBUP3DO00G}M08002LU2BM
    Log number____________ 0000000000019281314
    Created:
    Date__________________ 08/29/2008
    Time__________________ 02:10:00
    User__________________ BCKUSR
    Transaction code______ 
    Program_______________ /SAPAPO/SAPLCIF_GEN
    Operating mode________ B (Batch processing)
    Status:
    Expiry date___________ 09/05/2008
    Keep until expiry_____ Log can be deleted before expiry date
    Processing status_____ not specified
    ===

  • Sales order is blocked for single-item planning

    MD50 results in below
    Sales order  000010 is blocked for single-item planning
    Message no. 61211
    what are some possible causes?

    Hi Friend,
    Please check the status of the concerned sales order and validate it.

  • Block individual planned orders from CIF

    Hello All,
    I would like to know if there is a way to exclude individual planned orders from CIF transfer from R/3 to APO?
    Thanks and Regards

    Hi Gabriella,
    It would not make sense to modify the standard way of working of SAP APO only for 2 months.
    If you use any kind of enhancements, etc, you would need to later on remove it or deactivate it.
    Best option would be to make adjustments in your forecast so that SNP could plan additionally for this temporary demand. Otherwise create dummy sales orders in R/3 which would inflate the demand. But this would be feasible, only if you DON'T automatically confirm the Sales orders for delivery in some way, or if you could think of some way in which these Sales Orders do not get processed further in some way.
    Or, as you yourself mentioned, increase the safety stock temporarily, and later on (may be after 2 months), reduce it to the normal value. But especially closer to end of 2 month period, someone would need to manually adjust planned or production orders in R/3 to have data sanity. Similarly, action would be needed in APO also to have data in sync with R/3.
    You could have created the planned orders directly in R/3 and sent them across to APO, but this would increase the receipt situation, so SNP would then start planning for lower "net demand".
    PS: In such scenarios where business needs something temporarily and which can't fit in the standard process, it is best that we  convince them to have some workarounds which might not really sound like businesswise wise (in this case creating additional forecast).
    Thanks - Pawan

  • How to block changes in system generated Plan orders

    Hi,
    As after MRP RUN we get Planned order generated by the system,  with type LP  , I have a requirement that system generated plan order quanity cannot be cnhage by the user if plan order is generated for quanity 85  user should not make it 100 no quality chnages,  also the manual plan order type LP cannot be create manully it should be creat by system only,  and for manul other type of plan order type should be use,
    How to do this.
    regards,
    zafar

    Hi
    Firming can be used when you don't want certain planned orders to change during subsequent MRP runs.
    Say today you have created certain palnned orders.
    In a normal scenario, when you do the MRP run again, the planned order may get changed if the requirements have changed.
    However as a normal business practice, it is not desired to change the production plans everytime there is a change in the requirement...especially in the immediate future (maybe a week or so).
    We set this as the planning time fence depending on the MRP type settimg in the material master, you may have firm orders.
    MRP will also generate firm planned orders for materials with MRP type P1 to P4.
    In addition to the above, any planned order that is manually changed is also firmed.
    Hope this may help
    Regards
    BRSR

  • Set Availability Check to Exclude Planned Order

    Hi All,
    anyone know how to set the availability check so it will not include the planned order in the calculation ?
    I find one setting in SPRO, the path is :
    Sales & distribution ==>  Basic functions ==> availability check and Transfer of Requirements ==> Availability Check  ==> Availability Check with ATP Logic or Against Planning ==> Carry Out Control for Availability Check
    select one of the record, and update filed "Incl. Planned Orders".
    I've uncheck that field, but I can't get the appropriate result. When I create a new sales order, the availability check still take the planned order I created before into account.
    The problem is, my user want to prevent creating delivery before the goods are already put in the stock. So the planned order should not be considered in the availblity check.
    Thank you in advance
    Rudy

    Hi Rudy,
    Concept of availability check is to verify if the stock is available at the time of creation of sales order. If available, when it can be ready for delivery (as Packing, arranging for transportation, etc may have lead time) & if not available, when it would be available considering Packing, arranging for transportation, etc lead time.
    Availability check whether material is available on required delivery date (backward scheduling) or not. If not available on required delivery date, system will propose next available date (forward scheduling)
    1.     Define Checking Groups
    Menu Path: SPRO>SD>Basic Functions>Availability Check and Transfer of Requirements> Availability Check with ATP Logic or Against Planning>Define Checking Groups
    You define checking groups with which you specify the type of requirements records the system is to create when processing sales orders or deliveries
    2. Define Material Block for Other Users
    Menu Path: SPRO>SD>Basic Functions>Availability Check and Transfer of Requirements> Availability Check with ATP Logic or Against Planning>Define Material Block for Other Users.
    3 .Define Checking Groups Default Value
    Menu Path: SPRO>SD>Basic Functions>Availability Check and Transfer of Requirements> Availability Check with ATP Logic or Against Planning>Define Checking Groups Default Value.
    4. Carry out Control for Availability Check
    Menu Path: SPRO>SD>Basic Functions>Availability Check and Transfer of Requirements> Availability Check with ATP Logic or Against Planning>Carry Out Control for Availability Check.
    5. Define Procedure by Requirements Class
    Menu Path: SPRO>SD>Basic Functions>Availability Check and Transfer of Requirements> Availability Check with ATP Logic or Against Planning>Define Procedure by Requirements Class.
    6. Define Procedure for Each Schedule Line Category
    Menu Path: SPRO>SD>Basic Functions>Availability Check and Transfer of Requirements> Availability Check with ATP Logic or Against Planning>Define Procedure for Each Schedule Line Category.
    7. Determine Procedure for Each Delivery Item Category
    Menu Path: SPRO>SD>Basic Functions>Availability Check and Transfer of Requirements> Availability Check with ATP Logic or Against Planning>Determine Procedure for Each Delivery Item Category.
    8. Checking Rule for Updating Backorders
    Menu Path: SPRO>SD>Basic Functions>Availability Check and Transfer of Requirements> Availability Check with ATP Logic or Against Planning>Checking Rule for Updating Backorders.
    9. Define Default Settings
    Menu Path: SPRO>SD>Basic Functions>Availability Check and Transfer of Requirements> Availability Check with ATP Logic or Against Planning>Define Default Settings.
    Availability checks
    1. Availability check is an integral part of the business process that determines if the required delivery quantity can be met on a required delivery date. For this purpose the system takes into account pre-delivery activities such as scheduling for picking or packing times and the time taken to produce or obtain the material. It also performs several background functions such as Backorder processing, rescheduling and ATP quantities.
    2. Backorder processing: processing of a sales order that has not been fully confirmed or not confirmed at a certain delivery date.
    3. Rescheduling: is a proposal of how – confirmed quantities already assigned to a sales order can be reassigned to other sales orders that have a higher priority.
    4. Available to promise (ATP): is a process of checking the available quantities of a material. The ATP quantity consists of warehouse stock + planned receipts (incoming stock) – planned issues (outgoing stock). to examine stock on hand (CO09) proceed to logistics – sales & distribution – sales – environment – availability overview.
    5. Replenishment lead time (RLT): is the time taken for the material to become available either internally (in house production) or externally (from a vendor). The most important things to consider during an external procurement are purchasing and MRP 2 (procurement) views of MMR where the processing time for purchasing, planned delivery time and goods receipt processing time are taken into account. On the other hand internal procurement is based on in house production time (MRP 2 view) goods receipt processing time or alternatively RLT time, which is found on MRP 3 view.
    6. RLT (Replenishment Lead Time) is the time taken for the material to become available. RLT is only used when doing an ATP check (Available To Promise). The value of RLT for a material is specified on material master record.
    7. There are three types of availability checks –
    Check on basis of ATP quantities.
    Check against product allocation.
    Check against planning.
    Configuring Availability check through Checking Groups –
    1. The checking group + checking rule determine how the availability check is to be performed.
    2. The checking group determines whether and how the system checks the stock availability and generates requirements for material planning. The checking group defines what type of requirements will be passed on i.e. summarized requirements (daily/weekly) or individual requirements for each sales order.
    3. The checking rule applies to how the availability check is to be carried out at the transaction level. Note that you must define checking rules for each individual application such as for production orders for example. In Sales and Distribution, the checking rule is specified internally within the system and cannot be changed.
    4. The checking rule, in conjunction with the checking group, determines the scope of the availability check for every business operation; that is, which stocks, receipts and issues are to be included in the availability check and whether the check is to be carried out with or without the replenishment lead time.
    5. Briefly explaining the above – checking group determines which type of requirement to be passed on to MRP whether it be individual or summarized and checking rule which is at the transaction level and can be configured independently for each application module, determines which stocks, receipts and issues to be taken into account. For performing an availability check checking group has to work in conjunction with checking rule.
    6. Advantages of individual processing over summarized processing –
    Backorder processing is possible.
    You can access (MD04) order, line and schedule line individually which gives a greater control on available stock and requirements placed on stock.
    The system automatically uses individual requirements in case of special stock items.
    7. Required data for the Availability check to be carried out –
    The Availability check must be switched on at the requirement class level.
    The Availability check must be set at the schedule line level.
    A requirements type must exist by which the requirements class can be found.
    A plant must be defined in the sales order for each schedule line item (in other words plant must be defined for every material in MMR).
    A checking group must be defined in the material master record in the MRP3 screen in the availability check field.
    8. Configuring Availability check and defining Checking Groups –
    Checking groups are introduced into the sales order based on the setting in the material master record.
    SAP standard checking groups are 01 – summarized requirements and 02 – individual requirements or you can create your own by copying the standard ones.
    Total sales and total deliveries columns are there to configure a checking rule to sum up requirements to post to MRP either individually or by day or week.
    Block quantity required can be set if you want several users to be able to process the material simultaneously in different transactions without blocking each other.
    The no check indicator is CHECKED when you DO NOT want the system to carry out ATP check.
    9. Defining material block for other users – the block check box is an indicator that enables you to block material master records of a particular material during the availability check and restrict other users from accessing same master record and reserve the material. If the block is not set, two users can confirm the same material at the same time for two different orders, not knowing if the stock is available or not. If you select this field, the material is blocked during the availability check and other users cannot: a) Make changes in the material master record. b) Create purchase orders for the material. C) Create orders for the material.
    10. Defining default values for checking groups - Checking groups are introduced into the sales order based on the setting in the material master record.
    However if there is no entry present in the material master record for the checking group, a default value can be set here, depending on material type and plant.
    This default value will be used by the system depending on the material type mentioned in MMR and plant in sales order.
    If an entry exists, this default value is over written by MMR.
    11. Controlling Availability Check – in this section, you tell the system what stock on hand and what inward and outward movements of stock it must take into account when performing the availability check in addition to whether or not to consider the replenishment lead time.
    12. These settings are based on the checking group that is assigned to the material master record and the checking rule that is predefined and assigned to the sales and distribution transaction.
    13. These settings carry out control both for sales order and delivery as well. This is due to the fact that you may want to include specific stock or incoming stock for the sales order, yet at the time of the delivery only include physical stock on hand waiting to be shipped.
    14. It is possible to indicate to the system that you would like the availability check NOT TO CHECK the stock at the storage location level. This indicator is used to set the scope of the availability check.
    15. It is used to switch off the check at storage location level. You create a reservation for a particular storage location. However, the scope of the availability check is set in such a way as to exclude the storage location. In this case, the system carries out the check at plant level only and does not take the storage location into account that is specified in the reservation.
    16. Should you not want the system to automatically check RLT, you may indicate so here. RLT is the time taken for a material to become available. It is only used when doing an ATP check and is taken from MMR.
    17. Defining the elements in the availability check entirely depends on the business needs, but a few tips are given under –
    When controlling the Availability check at the time of the sales order, a purchase requisition does not necessarily indicate by it is going to come into the plant.
    A shipping notification on the other hand - a confirmed purchase order – is a good indicator of receiving stock on a specified date.
    It is always recommended not to select the shipping notifications for the delivery requirements type as you may not actually receive the stock into plant or warehouse for which you are creating a delivery.
    Please Reward If Helpful,
    Thanks and Regards,
    Sateesh.Kandula

Maybe you are looking for