Transfer of forecast from SNP to ECC

We are using transfer profile to transfer forecast (9ADFCST) from SNP to ECC.
We find that the original forecast is not transferred, but only the unconsumed  (Original fcst - sales) forecast is transferred.
Is there a way to transfer the original forecast from SNP to ECC?
Thanks,
Ashok

Hi JD,
Thanks for your response.
Yes, we had thought of doing that, but we are transferring the forecast based on requirement strategy for each product in product master data in SNP.
Though DP has all the original forecst, it does not have req. strat. as a selection criterion for SKU.
For example-- if the req. strat. is 20 then create VSF orders in ECC, if it is 30 then create VSE orders in ECC and if it is 32 do not transfer to ECC.
So we have to fall back on SNP to transfer the forecast using that product selection criterion.
But in SNP the forecast is consumed by sales order/deliveries and only the "remaining" forecast (after all the consumption have taken place) is transferred.
We had tried /sapapo/dmp2 to transfer original forecast, but it does not work if the "Planning Assembly" field is not checked in the product master. And we do not use that field in our product master data.

Similar Messages

  • Transfer orders from SNP to ECC

    Hello,
    Could anyone please tell me how to transfer planned orders (production, purchase & transport) from SNP to ECC?
    Thank you in advance for your help.
    David.

    Thank you Senthil for your answer.
    Production orders are now being transfer, but purchase and transport req. we are still having problems.
    We checked sapapo/ccr and there is an error: " CIF 182 - No external number exist in R/3". We still have not figure out what could be the problem. Any ideas of what could be the problem?
    Thanks,
    David
    Edited by: DToron on Sep 10, 2009 5:35 PM

  • Transfer supplier data from SRM to ECC

    Hi,
    As far as I know if we are using ROS only, then we can only have the one way synchronization from ECC to SRM. Thus in the process, if vendor register in ROS engine, then when we want to create the ECC vendor, we must create the data in ECC manually, and also link it manually as well.I know this for sure in SRM 5.0
    We are plannig to use SRM 7.0. Is this still the case? I also read somewhere that if we use SUS component, then t is possible for us to have vendor data in SRM synchronized to ECC.
    Is this true?
    Best regards,
    John

    Hi Nikhil,
    So you're saying that even if SUS is implemented and SRM_SUCO_1 is activated we still have to create supplier manually in ECC?
    I have checked the release note of SRM 7 and see this statement regarding SRM_SUCO_1:
    Supplier master replication to SAP SRM and SAP ERP back-end systems
    What does it mean by replication to SAP ERP back-end systems?
    Best regards,
    Yosea

  • Classic Scenario- Service Item custom field transfer from SRM to ECC

    Hello Experts,
    I was looking for a way to transfer custom fields from SRM to ECC(PR/PO) for service items.I am on SRM 7.01 and ECC 6.0 ehp 5.
    The same custom fields are getting transferred for Material item using the BADI BBP_CREATE_BE_RQ_NEW.
    But the same badi doesnt work for service item transfer.
    I would appreciate it if someone could help me with this.
    Regards,
    Cruiser

    You can use the Function Module SPOOL_RQ_CREATE with the parameters as bellow and debug.
    REQNO = SC number
    REQUIS_NUMBER = as Purchase Req no ( from backend )
    IV_BE_LOGSYS = backend logical system.
    System will go through the same path as SC bridging to PR.
    HTH,
    Chandu
    Edited by: Chandrahasan H on Mar 23, 2011 3:36 PM

  • How to transfer user defined accounting fields from SRM to ECC ?

    Hi!
    We are running SRM 5.0 and ECC 6.0 with classic scenario.
    We have defined Business entity filed account assignment tab in SRM SHC.
    New fields are also defined in tables BBP_C_ACC_F and in BBP_C_ACCFD and added in the structure also INCL_EEW_PD_ACC_CSF. New fields are also defined in srpo accounting.
    In R/3 the same field is already defined as it is standard one.
    When I create PR or PO i entered the Business entity for the account assignment R i.e real estate.
    However, when I order my shopping cart with values in new fields, the values are not transferred into backend.
    Standard fields transfer nicely, but the user defined fields dont transfer.
    Can any please let me know what we have to do for these user defined values to transfer to back end. We need to implement any BADI ?
    Please let me know
    Thanks

    Hi,
    Use  BADI  BBP_CREATE_PO_BACK ( t.code SE18) can transfer custom fields
    some useful links to transfer custom fields from SRM to ECC..
    Re: Purchase Order item customer fields
    implementation of BADI BBP_ECS_PO_OUT_BADI in SRM. and BBP_PO_INBOUND_BADI
    Re: Custom field values are not being transfered to the backend system
    Re: How to replicate SRM PO customer fields to ERP PO in ECS
    Update Custom Fields in PO - BBP_ECS_PO_OUT_BADI
    BBP_ECS_PO_OUT_BADI
    implementation of BADI BBP_ECS_PO_OUT_BADI in SRM. and BBP_PO_INBOUND_BADI
    Update Header Text in R/3 using BBP_ECS_PO_OUT_BADI
    Hope these are helpful..
    Thanks
    prasad .s

  • /SAPAPO/BP1  - Transfer of forecast

    Hello,
    I would like to transfer the forecast from APO to third party system.
    Can I use /sapapo/bp1 ?
    Thank you
    Regards
    Pratap

    This transaction  is sending the the transaction data, If it serve your purpose please use it.
    Send Transaction Data
    You can use this function to select and transfer transaction data (orders, stocks, and so on) to external (non-SAP) systems.
    This function can be used to transfer data that was created by an external system (or an SAP system) or locally in SAP APO. (The function is not meant for transferring data to SAP systems. To do this, use the relevant CIF transfer functions.)
    You can specify the following for the transfer:
    The objects (for example, sales orders, external procurement orders, and so on) that are selected and transferred, and the criteria used to do this.
    Possible Selection Criteria
    You can enter the product or locations to select the data. You can choose whether to use external names (as they are used in the BAPIs or the external system, for example) or internal names (as they are used in SAP APO). Only master data that is either known to or defined in the logical system or system group specified is selected.
    Alternatively, the data can be selected using order numbers. Note that in this case only objects can be selected that can have order numbers. (Stocks or planned independent requirements, for example, cannot then be transferred). Note also that there can also be many orders (for example, generated by SNP) without an order number. Orders that have been created by external systems are selected using the logical system specified. That is, only orders for the logical system specified are selected. All orders that are local to SAP APO (order type 8) are selected.
    Specify also which planning version is to be used and which objects (for example, stocks, orders, and so on) are to be transferred.
    Specify also whether the transfer is to be direct or whether the objects to be transferred should only be selected and displayed at first. If you set the indicator "Display Selections" the objects are selected and displayed. You can then transfer them in a later step.
    2. Extended Selection Criteria
    When selecting by location product you can also use the following selection criteria:
    By default, only orders that were created locally in SAP APO or transferred from the logical system specified are selected. In the case of planned independent requirements and stocks, all objects that exist in the system group specified are selected. You can also specify in the extended selections whether orders that are in the same system group but which were transferred from a different logical system are also to be selected.
    When selecting by location product (not order number), the following selection parameters are also available. In this case, only objects where at least one location product meets these criteria are selected.
    Selection by certain ATP categories. Note that you can only enter individual values for these selection criteria. You cannot enter intervals or exclude elements.
    You can specify whether only location products for certain planners are to be selected.
    Furthermore, you can also specify whether to select by receipt element only, requirements element only, or according to both. This is only possible for orders and not for stocks or planned independent requirements, for example. By default, the system searches for receipt and requirements elements. If you specify that the system is only to search for receipt elements, only orders/schedule lines are selected where the location products from the selection appear in the receipt elements. With the exception of VMI orders, selecting sales orders/deliveries in this way does not usually return useful results, since these consist solely of requirements elements.
    If, instead, you want to select by requirements element only, only orders/schedule lines are selected where the location products from the selection appear in the requirements elements. For stock transfers this means, for example, that you can also specify whether the selection should be based on requirements or receipts.
    For the "self-defined selection", you can enter any values that you want. Their interpretation depends on the customer implementation (BAdI implementation). Further technical details are provided at the end of this document.
    Selection by certain order types. Note that when entering values for these selection criteria you can only enter individual values. You cannot enter intervals or exclude elements.
    Selection by time interval. Only orders/planned independent requirements that lie either completely or partially within this time interval are transferred. This does not affect the transfer of stocks using object "StockAPS". The following information is necessary to specify a time interval:
    The type of time interval: That is, is a calendar day, calendar week, or a relative period of time entered.
    The start and end of the interval. The entry must be made in accordance with the type of time interval. For more information, see the F1 help for the time interval. Note that you cannot use the input help (F4) for this.
    You can optionally specify which time zone is used. The time stamps for the interval start and end are calculated from the interval specified and displayed in UTC time.
    When using a time interval to transfer requirements/receipt elements, note that making a selection according to start and/or end time only delivers useful results for objects that have actual dates/ times. Since stocks, for example, do not have dates/times, you are not advised, as a rule, to use these selection parameters for stocks.
    Specifying the selection mode: This is only possible in certain application cases, since restrictions exist. You must note these restrictions. For more information, see the F1 help for the selection mode.
    3. Log/Technical Transfer Parameters
    You can use these to specify how the data is to be sent and where is it to be sent to. You can also configure whether the selected data is to first be displayed before the transfer and then transferred in another step, or whether the transfer is to take place immediately.
    Send mode:
    You use the send mode to specify whether the data is to be sent as IDocs, tRFC, or both (if configured in Customizing).
    Target system:
    If you want to send the data to a particular target system, specify it here. The target system must be entered in Customizing correctly. The target system does not need to be specified if the distribution model is used, since the target systems are determined automatically in this case.
    Use distribution model:
    If the distribution model is used, the ALE distribution model is read and the target systems are determined automatically. If you do not want to send data to all target systems entered, specify the target system as described above.
    Display selections
    Here you can specify whether the selection results are displayed before the data is transferred. The data is then transferred in another step. This can be helpful when checking the size of the data selected, the correctness of the data, and the target systems that were found.
    The items "performance/packaging/error checks" and "transfer details" are dealt with later on.
    Integration
    Standard BAPIs are used for selecting and transferring the objects. The technical integration requires that you understand these BAPIs and objects (for example, which objects and data are selected and how the transfer works from a technical point of view, which fields are available, and so on).
    1.Which data can be selected and transferred:
    You can select and transfer the following objects or data. The transaction data must be available in SAP APO liveCache.
    "SalesOrderAPS" (BUS10501). This corresponds to sales orders, deliveries, and so on.
    The entire order (that is, with all items/schedule lines) is always transferred, as soon as an item matches the selection criteria.
    "ProcurementOrderAPS" (BUS10502). This corresponds to external procurement orders such as purchase orders, stock transfers, and so on.
    The entire order (that is, with all items/schedule lines) is always transferred, as soon as an item matches the selection criteria.
    "ManufactOrderAPS" (BUS10503). This corresponds to in-house production orders such as planned orders or production orders.
    The entire order is always transferred. If there are RPM components, these are also selected and transferred.
    "StockAPS" (BUS10504). This corresponds to stocks.
    "PlannedIndReqmtsAPS" (BUS10020). This corresponds to planned independent requirements.
    Requirements/receipt elements. This roughly corresponds to a requirements/stock list or product view.
    You can find the relevant interfaces (parameters, fields) for the "Receive" methods and the business objects in the BAPI Explorer. There you can also find the relevant ALE interfaces and function module interfaces for the "Receive" methods.
    2. How is the data transferred:
    The data is transferred using the interface objects or the following BAPIs (or ALE message types for the BAPIs):
    "ProductAPS.GetList2" is used to determine the location products for the object selection.
    Sales orders, deliveries,and so on:
    "SalesOrderAPS.GetList2" or "SalesOrderAPS.RequestList2" is used to select the data. The data is transferred using "IF10501.ReceiveList2".
    External procurement orders:
    "ProcurementOrderAPS.GetList2" or "ProcurementOrderAPS.RequestList2" is used to select the data. The data is transferred using "IF10502.ReceiveList2".
    In-house production orders:
    "ManufactOrderAPS.GetList2" or "ManufactOrderAPS.RequestList2" is used to select the data. The data is transferred using "IF10503.ReceiveList2".
    Stocks:
    "StockAPS.GetList2" or "StockAPS.RequestList2" is used to select the data. The data is transferred using "IF10504.ReceiveList2".
    Planned independent requirements:
    "PlannedIndReqmtsAPS.GetList" or "PlannedIndReqmtsAPS.RequestList" is used to select the data. The data is transferred using "IF10020.ReceiveList".
    Requirements/receipt elements:
    "PPDSServiceAPS.GetReqsReceipts" or "PlannedIndReqmtsAPS.RequestReqsReceipts" is used to select the data. The data is transferred using "IF10500.ReceiveReqsReceipts".
    If user exits or BAdI implementations are used within the BAPIs mentioned, you must take these into account since they are also run through. This can influence the result. You can also find more information about the named selection methods in the BAPI Explorer.
    3. What must be taken into account for the selection and transfer of data:
    The factors packaging, transfer type and error handling play an important role when selecting and transferring large volumes of data, in particular. Without packaging, for example, performance problems, memory overflows, or terminations can occur in the case of large volumes of data. This must be taken into account for both the sending (SAP APO) system and the receiving system. The main reason for this is that the entire volume of data is selected and transferred at once if packaging is not used. This may be desired and possible for a small number of objects. However, packaging is recommended for medium and large volumes of data. Since the package size depends on the data constellations, there is no "optimum" package size. For this reason, you must check which package size is most optimal for each scenario and data volume. When using ALE IDocs it is not recommended that you send IDocs with several thousand segments.
    3.1. You can use the setting "Performance/Packaging/Error Checks" to control the package size.
    You can specify a package size for location products when selecting data using location products. If the entry made is > 0, objects for the selected location products are transferred in various packages. If an order contains various location products, it is not split into several packages. Instead, an internal decision is made about the package or location product to which it is assigned for packaging.
    Package size per object type. Here you can specify the maximum number of orders, stocks, and so on that are to be contained within a package. This packaging occurs in addition to the packaging by location product described above. For example, 30,000 in-house production orders can exist for a location product. If packaging by location product, all 30,000 orders would be sent in one package. By packaging the orders per object type, the package containing 30,000 orders is split into smaller packages (for example, 300 * 100 orders). If no entry is made here, packaging does not occur for the relevant object type.
    Packaging for in-house production, external procurement, and sales orders/deliveries occurs on order level. That is, a package size of one means that one order is contained in one package.
    Packaging for planned independent requirements occurs on schedule line level (SCHEDID). That is, a package size of one means that one planned independent requirement for a location product is contained in one package.
    Packaging for stocks occurs on stock level. That is, a package size of one means that one stock for a location product is contained in one package.
    Packaging for requirements/receipt elements occurs on schedule line level, That is, a package size of one means that one schedule line (related to parameter IO_ELEMENTS) is contained in one package. Note that in the dependent parameters (for example, if order details or order headers for the schedule lines are transferred) redundant data may be transferred.
    You must also consider error handling, that is, how the system is to react to messages that may be generated. You can distinguish between three different error or message situations:
    Errors/messages during preselection
    Before the data is transferred, a preselection of objects is made to determine the objects to be transferred and to give the user an overview of the objects that match the selection. This preselection is displayed, for example, if you have chosen "Display Selections". If errors occur during the preselection, you can choose "Termt. If Select. Error Occurs" to specify that no objects are to be transferred and that the entire transaction is to be terminated.
    It is not usually advisable to transfer data if a serious error has occurred during the selection, since this would falsify the selection result. To nevertheless force the data to be transferred, you can deactivate "Termt. If Select. Error Occurs". This can be useful, for example, when errors occur that you know are not relevant to the transfer.
    If you do deactivate "Termt. If Select. Error Occurs", you must ensure that no incorrect selection results are transferred.
    Errors during object details selection
    When the transfer has been started, the detailed data for the objects orders, stocks, and so on)  is read according to the preselection quantity. (Error) messages can occur here. These messages are transferred by default to the target system in parameter RETURN_MESSAGES.
    You can control whether these messages are to be considered and, if so, how they are considered. The same is true for logging and displaying the messages.
    "Add to Log" specifies that these messages are added to the log. If they are not added, the user in the sending SAP APO cannot see if errors have occurred during the selection. The errors are simply transferred to the target system. The method of simply transferring the errors to the target system can be used if only the target system is to deal with error handling and not the sending system.
    If these messages are added to the log, you can also specify whether the messages are to determine whether or not the relevant package (for which errors have occurred) is to be transferred or not. The option "Always Transfer" means that messages do not influence the transfer. "No Transfer if Error or Termination Messages Occur" means that the relevant data package is not transferred, if these message types occur during the object details selection. A termination message for this package is then added to the log to show that the package was not transferred.
    "No Duplicate Messages" means that the number of messages in the log is reduced. If conversion errors occur, the same message can occur for several orders. This means that the message appears in the log several times, but contains different order numbers. To make it easier to see the errors in the log, you can suppress multiple duplicated messages.
    Errors during the technical transfer
    These include errors when generating IDocs or other errors of a technical nature that prevent the data package from being transferred or created. The relevant data package is displayed with a termination message in the log.
    In some cases you need to terminate processing, for example, when almost every package has errors (for example, caused by general system problems). It is then probably not advisable to continue processing as this would lead to long runtimes and many log errors (for the packages with errors). To avoid such situations, you can use the parameter "Max. Faulty Packages" to specify that processing is to be terminated once a certain number of faulty packages is exceeded. Note that this only refers to the number of packages that were not transferred and not to the error (messages) that have occurred in general.
    3.2. Transfer details
    A lot of data can exist for one object (for example, order, stock, and so on). An in-house production order, for example, has header data, receipt information, requirements, operations, activities, pegging information, and much other data that is contained in separate parameters in the interface. It takes time and memory space to read and transfer all of this data. In many cases, transferring all this detailed data is not necessary or desired. You can specify in the transfer details which detailed data is to be transferred or not transferred for which object or indeed for all objects. In this way, you can specify that pegging information for all objects is not to be transferred, for example.
    For performance reasons you are advised to only transfer the data that you actually need.
    By default, only the minimal data for the objects is transferred (for example, for in-house production orders only the order header data is transferred and no operations, activities, and so on are transferred).
    3.3 Miscellaneous
    Only errors that occur during the selection or creation of the packages are displayed in the log. The packages are considered to have been transferred or created successfully, as soon as it was possible to transfer them to the relevant middleware, (for example, IDoc was generated, tRFC was generated, and so on). If errors occur later on in processing (for example, IDoc could not be sent or tRFC could not be sent, because the target system is not available, and so on), these messages are not displayed in the log. Instead you must use the relevant monitoring option (depending on the transfer technique/middleware in use), for example IDoc Monitoring, or tRFC Monitoring, and so on).
    When packaging data by object type it can be the case (especially when sending requirements/stock lists) that data for an order is distributed across several packages. If, for example, when sending the requirements/stock list a package size of 1 is configured and an order exists with two items for the same location product, these two are shared between two packages. Since the same detailed data for the entire order (that is, both items) can be contained in each package, it could be the case that partially redundant information is contained in the packages that are transferred.
    BAdI definition "APO_BAPI_SENDTRANS" is available for enhancements.
    BAdI definitions (for example, "APO_BAPI_BUS10503" for in-house production) are also available in the RECEIVE interfaces. You can use these, for example, to implement a receive function (if the data is not to be sent to an external system, for example).
    Prerequisites
    You must specify the target system(s) to transfer the data. Depending on the means with which you want to transfer the data, you must be familiar with RFC or ALE Customizing. The following information is only meant as overview and does not go into details about the individual Customizing settings.
    A logical system must exist that represents the target system.
    In the ALE distribution model (transaction BD64) you must have configured which "Receive" calls are used for which target systems. For example, you can enter "IF10503.ReceiveList2" for in-house production orders. To do this, use "Insert BAPI". (Do not use "Insert Message Type".)
    Define an RFC destination (transaction SM59) for the target system, if the data is to be transferred using RFC.
    If the data is to be transferred using tRFC or RFC (that is, not transferred using ALE message types), assign an RFC destination to the BAPI method calls (for example, "IF10503.ReceiveList2"). You can do this in ALE Customizing (transaction BD97).
    When using ALE message types for the BAPI method calls, you must also make additional Customizing settings for partner agreements, ports, and so on.
    You must have authorization to display the planning version (C_APO_VERS) and for the transaction.
    Output
    Logging
    All objects that match the selection and can be transferred are written into the log. When using simulation mode, the selection result can be displayed before the data is transferred. An entry is created in the log for each object to be transferred. For objects that have multiple elements (for example, stock transfers or in-house production orders), not all components or location products are logged, for example. In the case of manufacturing orders, for example, not all components are logged. Instead one entry is made. In the case of stock transfers, for example, the source and destination are not logged. Instead one entry is made. The location product that was contained in the selection criteria is the one that is logged. If several location products from the selection are contained in an order, the location product from the selection that has the most "significance" is used, for example, the main product for in-house production orders or the receipt element for stock transfers.
    The location product that is specified in the log for an order/schedule line also determines the package in which this order is processed (for example, for packaging by location product).
    You should delete obsolete logs at regular intervals.
    How and to which target systems these objects are to be sent.
    Whether all detailed data for an object is to be transferred or only parts of it (for example, no characteristics information is transferred).
    These points will now be considered in detail.

  • CIFing the data from APO to ECC

    Hi - I know how to CIFing the data from ECC to APO. But i would like to know how  to transfer the data from APO to ECC.I also would like to know how to debug the code...I see some of the questions in this forum on CIF debugging, but they are all CIFing the data from ECC to APO, but i need the other way around ( APO to ECC )
    Could anyone provide me the detail steps to CIF debugging ?
    I really appreciate your help.

    Hi
    What kind of data do you want to transfer from APO to ECC ? Lets say you want to transfer live cache reqs generated by APO to R/3 and create firmed reqs , then the following are the prerequisites
    1. Make the publication setting /n/sapapo/cp1 as mentioned by DB
    2. Make sure the material -plant for which you want to transfer reqs is active in the PO/ Preq integration model in R/3
    3. In APO /n/sapapo/sdp110  make sure the transfer setting is set to immediate.
    Once all this is done , you dont have to do anything manually. The reqs will get transferred to R/3 automatically.
    Also we have to transfer master data from R/3 to APO since R/3 is the master and i dont think it is possible to do the opposite - transfer of master data from APO- R/3 (no standard tool available) . Also we generally transfer only live cache reqs and PIR's (demand plan) back to R/3 . For PIR's you need to use the transfer profile.
    Thanks
    Aparna
    Edited by: Aparna.Ranganathan on Feb 11, 2011 5:21 PM

  • Transferring Product Master Data Changes From APO to ECC/R/3

    Is it possible to transfer product master data changes in APO to ECC via the CIF?  If so, does it require custom coding?

    Hi James,
    In all the different clients where APO is being used with ECC systems. ECC system is always the main system (system of record) which contains all the master data and data present in ECC supposed to be the reference for APO system for planning purpose.
    Generally it is not recommended to transfer master data from APO to ECC but as mentioned earlier by some experts you may have ways to do that.
    I would be interested in the business scenario where one needs to transfer master data from APO to ECC.
    Thanks,
    Anupam
    Edited by: Anupam Sengar on Aug 11, 2011 12:31 AM

  • Issue in transfer of data from ECC to APO

    Hi All,
    I have a requirement of transferring data from ECC to APO. I am using EXIT_SAPLCMAT_001 fro this purpose. The problem is, I need to transfer the data of a field that is not present in cif_matloc but present in /sapapo/matloc.
    How should I proceed...Please help....this is an urgent requirement
    Thanks & Regards,
    SriLalitha

    Hi,
    you may want to go to the transaction /SAPAPO/SNP_SFT_PROF
    Determine Forecast of Replenishment Lead Time
    Use
    In this field, you specify how the extended safety stock planning determines
    the forecast of the replenishment
    lead time (RLT). The following values are available:
    Supply Chain
    The system determines the RLT forecast using the supply chain structure by
    adding the corresponding production, transportation, goods receipt, and goods
    issue times. If there are alternative procurement options, the system always
    takes the
    longest
    option into account.
    Master Data
    The system determines the RLT forecast from the location product master
    data.
    Master Data/ Supply Chain
    First, the system determines the RLT forecast from the location product
    master data. If no RLT forecast can be determined, the system determines the
    forecast using the supply chain structure (as described under
    Supply
    Chain
    Dependencies
    You can retrieve the replenishment lead time forecast yourself by using the
    GET_LEADTIME
    method of the Business Add-In (BAdI) /SAPAPO/SNP_ADV_SFT.
    Replenishment Lead Time in Calendar Days
    Number of calendar days needed to obtain the product, including its
    components, through in-house
    production or external
    procurement.
    Use
    The replenishment lead time (RLT) is used in the enhanced methods of safety
    stock planning in Supply Network Planning (SNP). The goal of safety
    stock planning is to comply with the specified service level, in order
    to be prepared for unforeseen demand that may arise during the replenishment
    lead time. The longer the RLT, the higher the planned safety stock level.
    Dependencies
    The field is taken into account by the system only if you have specified
    master data or master data/supply chain in the RLT: Determine
    Forecast field of the safety stock planning profile used.
    Hope this helps.
    The RLT from ECC is in MARC-WZEIT which is transferred to APO in structure /SAPAPO/MATIO field CHKHOR.
    May be if you maintain the setting in the profile, you may get the value in RELDT.
    Thanks.

  • Transfer purchase requsition from ecc to apo

    Hello,
    When creating purchase requirements in ECC, they are not transferred to APO although there is model integration. If I activate again the model, the pur req are trasnferred.
    In CCR
    It gives the error 181 in Schedule line does not exist in APO
    Schedule line does not exist in APO
    Message no. /SAPAPO/CIF181
    And the Queue is not bloqued, and the model is active.
    Thanks

    Hi Fernando,
    Based on the information given, it seems there is problem in
    activation.
    1) Check is there more than one model activated for purchase
    requisitons
    2) Check the master data (purchasing view) has been
    maintained for those items in R/3 level
    3) Check distribution definition is maintained in APO
    customisation
    4) I have a query in which, in general PR transfer will be
    from APO to R/3, in your case it is reverse, is there any
    business requirement?
    5) Check transfer to SNP orders to OLTP system in APO
    customisation
    Regards
    R. Senthil Mareeswaran.

  • Error logs in job releases forecast from DP to SNP-"Matl does not exist"

    Hi Everyone,
    I am facing error logs in the batch job which releases forecast from DP to SNP
    Forecast release job - Weekly - Through background job
    Forecast category - FA
    Error 1: - Characteristic combination appears on batch job log with an error that
    "GMC does not exist " Even though it exist in R/3 and APO
    All products with error message "Product does not exist" from do exist and have Forecast in Product View
    Error 2: - Deleted KCC keep showing up on the Demand Forecast release job log as errors even though they are invalid KCC and were deleted previously. How do they get removed from error log so they don't get created again
    Material does not exist on the APO Product Master, in R3 there is a delete flag and the MRP type is set to X1 ,it does not exist in the APO Product Master and does not exist in R3.
    Request you to kindly provide any way forward which may be causing error logs of the job
    Thanks in advance,
    Mrigendra Sharma

    Hi Mrigendra,
    Please re-initialize the SNP planning area (program : /SAPAPO/TS_PAREA_INITIALIZE) and then check the consistency by executing the program: /SAPAPO/TS_LCM_CONS_CHECK. If you observe any inconsistency in the log/spool, then re-run the program: /SAPAPO/TS_LCM_CONS_CHECK to observe all green.
    It is recommended to run the consistency program after any master data change. The initialization program should be run at least weekly.
    Try transfering the data again from DP to SNP to see if the error reappear.
    Hope this helps.
    Regards,
    Nawanit

  • Transfer field Value from ECC to APO

    Hi,
    I want to transfer a field from material master to APO. For this i am, using a CIF user exit... The field is not available in the ECC side (EXIT_SAPLCMAT_001), but i found a user exit on APO which has this field (EXIT_SAPMMDUSER_005) which i m not sure if it is called.. please help...

    Hi,
    Could you please send the details..What field you are checking..Field name ?
    You can explore the below 2 table in ECC EXIT EXIT_SAPLCMAT_001. It has the option for expansion.
    OT_CIF_MATKEYCUS
    OT_CIF_MATLOCCUS
    Thanks
    RKS

  • Release Of Forecast From DP To SNP (For Some Locations, Only Baseline)

    Dear All,
    Generally, we follow the following procedure....In the month begining, we generate the baseline forecast for all the locations (we are having around 20 branches). Then we used to open the DP planning book for a couple of days to our branch persons so that they are able to feed their correction. After which we release the final forecast i.e. Baseline Forecast +/- Branch correction to SNP for further proceesing.
    This month, we opened the planning book (as usual). Branches did  the branch correction. But on final checking, we found that around 4 -  5 branches have done corrections / updations very vagely i.e. roughly. So, we wants to ignore their branch correction.
    My query be that is it possible that while releasing the Forecast from DP to SNP... can we release baseline forecast for selective five branches and for the rest of the branches, we wants to release final forecast key figure i.e. Baseline +/- Branch correction.
    Kindly advise further.
    With Best Regards,
    Sanjeev Chugh
    17-NOV-2010 (AN)

    Sanjeev
    You have not mentioned at what level you are doing the forecasting. If forecasting is done at material- branch level then what you are asking can be achieved easily. All you have to do is go to /n/sapapo/mc90 ( or create a release profile) and for the branches for which you want to release baseline forecast , you have to specify the baseline forecast keyfigure in the input and specify the material branches in the i/p criteria. For adjusted forecast you have to use another variant and specify the adjusted forecast key figure and the corresponding material branches.
    Iam not sure how your requirement can be achieved in case you are forecasting @ material level.
    Thanks
    Aparna

  • Unable to transfer Purchase Requisition from ECC to EBP

    Dear Friends.
    We are unable to transfer PR from ECC to EBP. System issue stop message in SLG1 transaction for object BBP_EXTREQ
    Stop Message Type: Document type for determined backend system is missing.
    Warning Message Type: Grant 1111 does not exist.
    As per configuration guide we have performed following setting in EBP client
    1. We have created organization unit “Entry Channel” under company code.
    2. Under Entry Channel we create Local Purchasing Organization.
    3. Under Loc Purchasing Org we created Local Purchasing Group with
        - attribute BUK as backend company code
        - attribute BSA as backend PR type (NB)
        - this group is responsible for Entry channel procurement (setting in Function tab)
    4. Under Loc Purchasing Group we assigned RFC user which is same defined as RFC user in both EBP and ECC client.
        - attribute DP_PROC_TY defined as backend ECC PO type (NB)
    5. Attribute CUR define for entry Channel.
    6. Remote connection established with the same user defined under Organization Unit
    7. Remote user has profile sap_all and sap_new authorization.
    8. Material group, Material Type and Vendors are replicated from backend system.
    9. Sourcing always allowed is set for all product categories in “Define sourcing for Product Category”.
    10. Extended Classic Scenario is active.
    11. Defined Tolerance check and assigned TOG attribute.
    Performed following setting in ECC client.
    12. Defined RFC connection and user same as defined in Organization unit.
    13. Defined profile which reference to EBP logical system
    14. Maintained table V_T160EX with Material group/Pur group/ Profile combination.
    Finally transfer Purchase Requisition from ECC to EBP via report BBP_EXTREQ_TRANSFER. Further the outbound Queue fails with status ANORETRY. Also the log displayed the error ‘Application aborted due to serious problems’
    SLG1 in EBP issues stop message “Document type for determined backend system missing” and warning message “Grant 1111 does not exist”.
    Any idea what could be the reason?
    Please help!!
    Sandeep

    Hi
    It seems there is some problem with the Configuaration settings in SRM as well as R/3 side.
    <u>Anyways, please have a look at the following links, which might help.</u>
    <b>Direct Procurement</b>
    http://help.sap.com/saphelp_srm50/helpdata/en/b7/15d4396898042fe10000000a114084/frameset.htm
    <b>Prerequisites for External Requirements</b>
    http://help.sap.com/saphelp_srm50/helpdata/en/18/db183d30805c59e10000000a114084/frameset.htm
    <b>Attributes for the SRM Scenario</b>
    http://help.sap.com/saphelp_srm50/helpdata/en/84/a7e3389870c05ce10000000a114084/frameset.htm
    <b>Direct Material Scenario: Other Planned External Requirements</b>
    http://help.sap.com/saphelp_srm50/helpdata/en/6a/4b9e3b891da20ee10000000a114084/frameset.htm
    <b>Number range settings</b>
    http://help.sap.com/saphelp_srm50/helpdata/en/5d/fd7d3cb7f58910e10000000a114084/frameset.htm
    http://help.sap.com/saphelp_srm50/helpdata/en/b7/15d4396898042fe10000000a114084/frameset.htm
    <b>Define Transaction types</b>
    http://help.sap.com/saphelp_srm50/helpdata/en/10/fd7d3cb7f58910e10000000a114084/frameset.htm
    <b>Direct Material Scenario with Planning in SAP APO</b>
    http://help.sap.com/saphelp_srm50/helpdata/en/d3/4b9c3b122efc6ee10000000a114084/frameset.htm
    Hope this will help.
    Regards
    - Atul

  • BBP_PO_INBOUND_BADI:Transfer value from SRM to ECC PO custom field

    Hello, everyone
         Our SRM version is 7.13 with classic scenario,  ECC version is 6.17.  transferring quotation data to ECC for creating PO by PI.
        I created a custom field such as Z1 for PO in ECC ,  I need transfer someone value from SRM to Z1 when press 'create PO' in quotation,
    So  I have to use BADI:BBP_PO_INBOUND_BADI in ECC before PO generating,  but I found the breakpoint can not  reach this BADI, Why ?  how should I do?
    I used to apply normally  this BADI in SRM7.02 and ECC6.05  without PI  with extend classic scenario.
    Thanks very much
      Jesse.

    Hi Jesse,
    I think the BBP_PO_INBOUND_BADI  is used to enhance the data when the PO is sent via BAPI.
    Please check the PI interface name that you are using and find out the Proxy name (in Tcode: SPROXY) and find an Enhancement spot (either in SRM or in ECC).
    Regards
    Venkat

Maybe you are looking for