What are APO orders in APO (APO Order transaction:-SAPAPO/SNPTLB)?

Hi Experts,
Basically, am ABAP developer, but, i got a statement as below, regarding the APO,
User Exit of EXIT_SAPMSNPUSER_006 was used for the APO Order transaction:-SAPAPO/SNPTLB.
- What is the APO Order transaction:-SAPAPO/SNPTLB?
- What are the APO orders? Are they are planned orders, like PLNUM field in PLAF tbl?
- Why this transaction is used?
- What could be the business requiremnt behind this development?
- Any other info?
If my question is wake, sorry! Replies are gretaely appreciated.
thanq
Edited by: SAP ABAPer on Mar 29, 2009 7:09 PM

Hi,
Transaction /sapapo/snpylb is a transaction for Transport Load builder.
It does an optimised load build.
It is used to create transport loads once the deployment is carried out.
Once the load is created and you hit save, the user exit EXIT_SAPMSNPUSER_006 gets called.
When one creates the load, APO assigns an internal no to the id.
We had used this user exit to generate a custom no once the user hits save.
Hope you find this information useful!

Similar Messages

BADI / User Exit for APO Order transaction /SAPAPO/SNPTLB

Hi Experts,
We have a proxy interface and currently we are using FUNCTION EXIT_SAPMSNPUSER_006 for the APO Order transaction: /SAPAPO/SNPTLB.
This exist is triggering before the Order is being saved in APO and at times it is throwing an error 'Order key already exists in live cache' in the APO system.
Is there any other BADI or User exit available to Save the order in APO before the interface gets processed?, if so, plese guide me.
Thanks & Regards,
Vijaya

Hello Lakshmi,
I am having the same issue with the message "Order key already exists in live cache" in our system.
We are using the user-exit EXIT_SAPMSNPUSER_005 for UoM conversion. But we are not making any explicit proxy calls
to /SAPAPO/SNPTLB. Does the system automatically call this transaction with this user-exit?
Did you get a resolution for the issue. I would really appreciate if you can let me know how you have addressed this.
Thanks,
Ratnam

What are the disadvantages of implementing APO- Demand Planning without improvements or cleaning up the MRP. in other words is DP implementation dependant on MRP process. Gurus please advise

HI All. What are the disadvantages of implementing APO- Demand Planning without improvements or cleaning up the MRP. in other words is DP implementation dependant on MRP process. Gurus please advise

Hi Amol,
DP is the demand planning machine, here you estimate your forecast (future sales).
The MRP is a supply planning machine, here you use estimate the replenishment.
Both machines in a technical perspective are independent one each other. Now in a business perspective they are not: The problem that you will have if you don´t clean your MRP elements is not a problem in DP itself. I mean, you can have a very success implementation in DP, your forecast accuracy will be very good.. and you will get a very good forecast, but when the MRP run and estimate the replenishment, the effort that you made in DP will not be translated in good results and your planning situation will be still not good.
Kind Regards,
Mariano

What are the User Exits for Sales Order creation process?

Hi,
what are the User Exits for Sales Order creation process? how can I find them?
thanks in advance,
will reward,
Mindaugas

Please check this info:
User Exits In Sales Document Processing
This IMG step describes additional installation-specific processing in sales document processing. In particular, the required INCLUDES and user exits are described.
Involved program components
System modifications for sales document processing affect different areas. Depending on the modification, you make the changes in the program components provided:
MV45ATZZ
For entering metadata for sales document processing. User-specific metadata must start with "ZZ".
MV45AOZZ
For entering additional installation-specific modules for sales document processing which are called up by the screen and run under PBO (Process Before Output) prior to output of the screen. The modules must start with "ZZ".
MV45AIZZ
For entering additional installation-specific modules for sales document processing. These are called up by the screen and run under PAI (Process After Input) after data input (for example, data validation). The modules must start with "ZZ".
MV45AFZZ and MV45EFZ1
For entering installation-specific FORM routines and for using user exits, which may be required and can be used if necessary. These program components are called up by the modules in MV45AOZZ or MV45AIZZ.
User exits in the program MV45AFZZ
The user exits which you can use for modifications in sales document processing are listed below.
USEREXIT_DELETE_DOCUMENT
This user exit can be used for deleting data which was stored in a separate table during sales document creation, for example, if the sales document is deleted.
For example, if an additional table is filled with the name of the person in charge (ERNAM) during order entry, this data can also be deleted after the sales order has been deleted.
The user exit is called up at the end of the FORM routine BELEG_LOESCHEN shortly before the routine BELEG_SICHERN.
USEREXIT_FIELD_MODIFICATION
This user exit can be used to modify the attributes of the screen fields.
To do this, the screen fields are allocated to so-called modification groups 1 - 4 and can be edited together during a modification in ABAP. If a field has no field name, it cannot be allocated to a group.
The usage of the field groups (modification group 1-4) is as follows:
Modification group 1: Automatic modification with transaction MFAW
Modification group 2: It contains 'LOO' for step loop fields
Modification group 3: For modifications which depend on check tables or on other fixed information
Modification group 4: is not used
The FORM routine is called up for every field of a screen. If you require changes to be made, you must make them in this user exit.
This FORM routine is called up by the module FELDAUSWAHL.
See the Screen Painter manual for further information on structuring the interface.
USEREXIT_MOVE_FIELD_TO_VBAK
Use this user exit to assign values to new fields at sales document header level. It is described in the section "Transfer of the customer master fields into the sales document".
The user exit is called up at the end of the FORM routine VBAK_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBAP
Use this user exit to assign values to new fields at sales document item level. It is described in the section "Copy customer master fields into the sales document".
The user exit is called up at the end of the FORM routine VBAP_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBEP
Use this user exit to assign values to new fields at the level of the sales document schedule lines.
The user exit is called up at the end of the FORM routine VBEP_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBKD
Use this user exit to assign values to new fields for business data of the sales document. It is described in the section "Copy customer master fields into sales document".
The user exit is called up at the end of the FORM routine VBKD_FUELLEN.
USEREXIT_NUMBER_RANGE
Use this user exit to define the number ranges for internal document number assignment depending on the required fields. For example, if you want to define the number range depending on the sales organization (VKORG) or on the selling company (VKBUR), use this user exit.
The user exit is called up in the FORM routine BELEG_SICHERN.
USEREXIT_PRICING_PREPARE_TKOMK
Use this user exit if you want to include and assign a value to an additional header field in the communication structure KOMK taken as a basis for pricing.
USEREXIT_PRICING_PREPARE_TKOMP
Use this user exit if you want to include or assign a value to an additional item field in the communication structure KOMP taken as a basis for pricing.
USEREXIT_READ_DOCUMENT
You use this user exit if further additional tables are to be read when importing TA01 or TA02.
The user exit is called up at the end of the FORM routine BELEG_LESEN.
USEREXIT_SAVE_DOCUMENT
Use this user exit to fill user-specific statistics update tables.
The user exit is called up by the FORM routine BELEG-SICHERN before the COMMIT command.
Note
If a standard field is changed, the field r185d-dataloss is set to X. The system queries this indicator at the beginning of the safety routine. This is why this indicator must also be set during the maintenance of user-specific tables that are also to be saved.
USEREXIT_SAVE_DOCUMENT_PREPARE
Use this user exit to make certain changes or checks immediately before saving a document. It is the last possibility for changing or checking a document before posting.
The user exit is carried out at the beginning of the FORM routine BELEG_SICHERN.
User exits in the program MV45AFZA
USEREXIT_MOVE_FIELD_TO_KOMKD
Use this user exit to include or assign values to additional header fields in the communication structure KOMKD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
USEREXIT_MOVE_FIELD_TO_KOMPD
Use this user exit to include or assign values to additional item fields in the communication structure KOMPD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
USEREXIT_MOVE_FIELD_TO_KOMKG
Use this user exit to include or assign values to additional fields in the communication structure KOMKG taken as a basis for material determination and material listing. This is described in detail in the section "New fields for listing/exclusion".
USEREXIT_MOVE_FIELD_TO_KOMPG
Use this user exit to include or assign values to additional fields in the communication structure KOMPG taken as a basis for material determination and material listung. This is described in detail in the section "New fields for listing/exclusion".
USEREXIT_REFRESH_DOCUMENT
With this user exit, you can reset certain customer-specific fields as soon as processing of a sales document is finished and before the following document is edited.
For example, if the credit limit of the sold-to party is read during document processing, in each case it must be reset again before processing the next document so that the credit limit is not used for the sold-to party of the following document.
The user exit is executed when a document is saved if you leave the processing of a document with F3 or F15.
The user exit is called up at the end of the FORM routine BELEG_INITIALISIEREN.
User-Exits in program MV45AFZB
USEREXIT_CHECK_XVBAP_FOR_DELET
In this user exit, you can enter additional data for deletion of an item. If the criteria are met, the item is not deleted (unlike in the standard system).
USEREXIT_CHECK_XVBEP_FOR_DELET
In this user exit, you can enter additional data for deletion of a schedule line. If the criteria are met, the schedule line is not deleted (unlike in the standard system).
USEREXIT_CHECK_VBAK
This user exit can be used to carry out additional checks (e.g. for completion) in the document header. The system could, for example, check whether certain shipping conditions are allowed for a particular customer group.
USEREXIT_CHECK_VBAP
This user exit can be used to carry out additional checks (e.g. for completion) at item level.
USEREXIT_CHECK_VBKD
The user exit can be used to carry out additional checks (e.g. for completion) on the business data in the order.
USEREXIT_CHECK_VBEP
This user exit can be use to carry out additional checks (e.g. for completion) on the schedule line. During BOM explosion, for example, you may want certain fields to be copied from the main item to the sub-items (as for billing block in the standard system).
USEREXIT_CHECK_VBSN
You can use this user exit to carry out additional checks (e.g. for completion) on the serial number.
USEREXIT_CHECK_XVBSN_FOR_DELET In this user exit, you can enter additional criteria for deletion of the serial number. If the criteria are met, the serial number is not deleted (unlike in the standard system).
USEREXIT_FILL_VBAP_FROM_HVBAP
You can use this user exit to fill additional fields in the sub-item with data from the main item.
USEREXIT_MOVE_FIELD_TO_TVCOM_H
You can use this user exit to influence text determination for header texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
USEREXIT_MOVE_FIELD_TO_TVCOM_I
You can use this user exit to influence text determination for item texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
User-Exits for product allocation:
The following user exits all apply to structure COBL, in which the data for account determination is copied to item level.
USEREXIT_MOVE_FIELD_TO_COBL
Option to include new fields in structure COBL.
USEREXIT_COBL_RECEIVE_VBAK
Option to assign values from the document header to the new fields.
USEREXIT_COBL_RECEIVE_VBAP
Option to supply values from the item to the new fields.
USEREXIT_COBL_SEND_ITEM
A changed field can be copied from the structure into the item. You could use the user exit to display a certain field in the account assignment block (see also MV45AFZB).
USEREXIT_COBL_SEND_HEADER
A changed field can be copied from the structure to the header (see source text MV45AFZB)
USEREXIT_SOURCE_DETERMINATION
You can use this user exit to determine which plant will be used for the delivery. In the standard system, the delivering plant is copied from the customer master or the customer-material info record. If you want to use a different rule, then you must enter it in this user exit.
USEREXIT_MOVE_FIELD_TO_ME_REQ
With this user exit you can include additional fields for the following fields:
EBAN (purchase requisition)
EBKN (purchase requisition-account assignment)
USEREXIT_GET_FIELD_FROM_SDCOM
Option to include new fields for the variant configuration. Fields that are included in structure SDCOM can be processed and then returned to the order.
USEREXIT_MOVE_WORKAREA_TO_SDWA
You can use this user exit to format additional work areas for the variant configuration. You will find notes on the user exit in MV45AFZB.
User-Exits for first data transfer:
The following user exits can only be used for the first data transfer.
Note
Only use the user exits if the names/fields do NOT have the same name.
USEREXIT_MOVE_FIELD_TO_VBAKKOM
Option to include additional fields in structure VBAKKOM (communiction fields for maintaining the sales document header)
USEREXIT_MOVE_FIELD_TO_VBAPKOM
Option to include additional fields in structure VBAPKOM (communication fields for maintaining a sales item)
USEREXIT_MOVE_FIELD_TO_VBEPKOM
Option to include additional fields in structure VBEPKOM (communication fields for maintaining a sales document schedule line)
USEREXIT_MOVE_FIELD_TO_VBSN
You can use this user exit to include fields in structure VBSN (scheduling agreement-related change status).
USEREXIT_MOVE_FIELD_TO_KOMKH
You can use this user exit to include new fields for batch determination (document header).
USEREXIT_MOVE_FIELD_TO_KOMPH
You can use this user exit to include new fields for batch determination (document item).
USEREXIT_CUST_MATERIAL_READ
You can use this user exit to set another customer number in the customer material info record (e.g. with a customer hierarchy)
USEREXIT_NEW_PRICING_VBAP
Option for entry of preconditions for carrying out pricing again (e.g. changes made to a certain item field could be used as the precondition for pricing to be carried out again). Further information in MV45AFZB.
USEREXIT_NEW_PRICING_VBKD
Option for entry of preconditions for carrying out pricing again (e.g. changes to the customer group or price group could be set as the preconditions for the system to carry out pricing again). Further information in MV45AFZB.
User-Exits in Program MV45AFZD
USEREXIT_CONFIG_DATE_EXPLOSION
The BOM is exploded in the order with the entry date. You can use this user exit to determine which data should be used to explode the BOM (explosion with required delivery date, for example).
User exits in the program FV45EFZ1
USEREXIT_CHANGE_SALES_ORDER
In the standard SAP R/3 System, the quantity and confirmed date of the sales document schedule line is changed automatically if a purchase requisition is allocated, and it or the sales document is changed (for example, quantity, date).
If you want to change this configuration in the standard system, you can define certain requirements in order to protect your sales orders from being changed automatically. Use this user exit for this purpose. Decide at this point whether the schedule lines are to be changed.
User-Exits in Program RV45PFZA
USEREXIT_SET_STATUS_VBUK
In this user exit you can you can store a specification for the reserve fields in VBUK (header status). Reserve field UVK01 could, for example, be used for an additional order status (as for rejections status, etc.).
The following workareas are available for this user exit:
VBUK (header status)
FXVBUP (item status)
FXVBUV (Incompletion)
USEREXIT_SET_STATUS_VBUP
In this user exit you can you can store a specification for the reserve fields for VBUP (item status).
The following workareas are available for this user exit:
FXVBAP (Item data)
FXVBAPF (Dynamic part of order item flow)
FXVBUV (Incompletion)
USEREXIT_STATUS_VBUK_INVOICE
You can use this user exit to influence billing status at header level.
User exits in the screens
Additional header data is on screen SAPMV45A 0309, additional item data on screen SAPMV45A 0459. These screens contain the Include screens SAPMV45A 8309 or SAPMV45A 8459 as user exits.
Fields which are also to be included in the sales document for a specific installation should be included on the Include screens for maintaining. If an application-specific check module is needed for the fields, this can be included in the Include MV45AIZZ. The module is called up in the processing logic of the Include screens.
For field transports, you do not have to make changes or adjustments.
Example
A new field, VBAK-ZZKUN, should be included in table VBAK.
If the check is defined via the Dictionary (fixed values or check table) the field must be included with the fullscreen editor in the Include screen SAPMV45A 8309. In this case, no change has to be made to the processing logic.
User Exits in Program MV45AFZ4
USEREXIT_MOVE_FIELD_TO_KOMK
You can use this user exit to add or edit additional header fields in the communication structure - KOMK- for free goods determination. For more information, see the New Fields for Free Goods Determination IMG activity.
USEREXIT_MOVE_FIELD_TO_KOMP
You can use this user exit to add or edit additional item fields in the communication structure KOMP for free goods determination. For more information see the New Fields for Free Goods Determination IMG activity.
User Exits in the SAPFV45PF0E and SAPFV45PF0C Programs
EXIT_SAPFV45P_001
You can use this user exit to decide whether intercompany billing data is used in the profitability segment for cross-company code sales, or whether the data comes from external billing (external customer, sales data from the selling company code.
Regards
Eswar

BADI/User Exit for APO Transaction: /SAPAPO/SNPTLB

Hi Experts,
We have a proxy interface and currently we are using FUNCTION EXIT_SAPMSNPUSER_006 for the APO Order transaction: /SAPAPO/SNPTLB.
This exist is triggering before the Order is being saved in APO and at times it is throwing an error 'Order key already exists in live cache' in the APO system.
Is there any other BADI or User exit available to Save the order in APO before the interface gets processed?, if so, plese guide me.
Thanks & Regards,
Vijaya

Hello Lakshmi,
I am having the same issue with the message "Order key already exists in live cache" in our system.
We are using the user-exit EXIT_SAPMSNPUSER_005 for UoM conversion. But we are not making any explicit proxy calls
to /SAPAPO/SNPTLB. Does the system automatically call this transaction with this user-exit?
Did you get a resolution for the issue. I would really appreciate if you can let me know how you have addressed this.
Thanks,
Ratnam

What are the tables corresponding to sales order - parners

Hi Folks,
Can u pls let me know what are the corresponding tables n fileds for the va02->parners i.e sold to party, ship to party etc, buyer , bill to party and contact details , adress of these parners wil store.
Thanks in advance.
Regards
Rajesh

hii i am sending u the full code thta i had designed for my sales order confirmation using sap script
TABLES: VBAK,
        ADRC,
        VBPA,
        VBAP,
        SPELL.
DATA: BEGIN OF TVBAK OCCURS 0,
      VBELN LIKE VBAK-VBELN,
      AUDAT LIKE VBAK-AUDAT,
      KUNNR LIKE VBAK-KUNNR,
      VKORG like VBAK-VKORG,
      END OF TVBAK.
DATA: BEGIN OF TADRC OCCURS 0,
      ADDRNUMBER LIKE ADRC-ADDRNUMBER,
      NAME1 LIKE ADRC-NAME1,
      NAME2 LIKE ADRC-NAME2,
      CITY1 LIKE ADRC-CITY1,
      POST_CODE1 LIKE ADRC-POST_CODE1,
      COUNTRY LIKE ADRC-COUNTRY,
      KUNNR LIKE VBPA-KUNNR,
      VBELN LIKE VBPA-VBELN,
      END OF TADRC.
DATA:BEGIN OF TVBPA OCCURS 0,
     ADRNR LIKE VBPA-ADRNR,
     KUNNR LIKE VBPA-KUNNR,
     VBELN LIKE VBPA-VBELN,
     END OF TVBPA.
DATA: BEGIN OF TVBAP OCCURS 0,
      POSNR LIKE VBAP-POSNR,
      VBELN LIKE VBAP-VBELN,
      MATNR LIKE VBAP-MATNR,
      ARKTX LIKE VBAP-ARKTX,
      KWMENG LIKE VBAP-KWMENG,
      VRKME LIKE VBAP-VRKME,
      NETWR LIKE VBAP-NETWR,
      WAERK LIKE VBAP-WAERK,
      END OF TVBAP.
DATA :W_VBELN LIKE VBAK-VBELN,
      s_amount like vbap-netwr ,
      amount_word LIKE SPELL.
selection-screen: begin of block b1.
select-options: s_vbeln for vbpa-vbeln no intervals no-extension.
selection-screen: end of block b1.
*AT SELECTION-SCREEN.
SELECT VBELN INTO W_VBELN FROM VBAK
      WHERE VBELN IN S_VBELN.
*ENDSELECT.
START-OF-SELECTION.
SELECT VBELN AUDAT KUNNR VKORG FROM VBAK INTO CORRESPONDING
FIELDS OF
TABLE TVBAK WHERE VBELN IN
S_VBELN.
   IF SY-SUBRC <> 0.
     MESSAGE I398(00) WITH 'NO DATA'.
   ENDIF.
SELECT NAME1 NAME2 CITY1 POST_CODE1 COUNTRY FROM ADRC INTO
CORRESPONDING
FIELDS OF
TABLE TADRC.
   IF SY-SUBRC <> 0.
     MESSAGE I398(00) WITH 'NO DATA1'.
   ENDIF.
SELECT ADRNR KUNNR VBELN FROM VBPA INTO CORRESPONDING
FIELDS OF
TABLE TVBPA WHERE PARVW = 'WE'.
   IF SY-SUBRC <> 0.
     MESSAGE I398(00) WITH 'NO DATA2'.
   ENDIF.
SELECT VBELN POSNR MATNR ARKTX KWMENG VRKME NETWR WAERK FROM VBAP INTO
CORRESPONDING
FIELDS OF TABLE TVBAP WHERE VBELN IN
S_VBELN.
IF SY-SUBRC <> 0.
   MESSAGE I398(00) WITH 'NO DATA3'.
   ENDIF.
LOOP AT TADRC.
   READ TABLE TVBPA WITH KEY ADRNR = TADRC-ADDRNUMBER.
      IF SY-SUBRC = 0.
       MOVE TVBPA-KUNNR TO TADRC-KUNNR.
       MOVE TVBPA-VBELN TO TADRC-VBELN.
       MODIFY TADRC.
      ENDIF.
ENDLOOP.
****reward if helpfull ******

What are the steps to send sales order custom field from CRM to ECC

Hi Xperts,
We have created a custom field in sales order [ VBAK] and successfully replicate its value from ECC to CRM. But while doing the enhancement to replicate the field value from CRM to ECC [ When the SO is created in CRM ] we are not able to do so.
We used a FM in CRM0_300, but while replicating the SO from CRM to R/3 it is not getting called.
Please help us by providing the steps to do the full enhancement to replicate the custom field of SO from CRM to ECC.
Thanks in Advance.

Hi Anjaneyulu,
We are faced with a similar situation as you.
Here is our scenario with the steps that we performed so far:
1. We have added a few custom fields in CRM 7.0 (Ehp1) using AET.
The BDoc BUS_TRANS_MSG has been automatically extended with these custom fields.
2. On ECC side also, same custom fields have been added to VBAK and VBAP, using APPEND STRUCTURE. Fields were added to ADDITIONAL DATA TAB B in VA01 / VA02 transactions.
3. Extended BAPI structures BAPISDITM and BAPISDITMX in both CRM and R/3 Side.
4. As mentioned in the note 1053817, we have implemented BADI CRM_DATAEXCHG_BADI -> Method CRM_DATAEXCH_AFTER_BAPI_FILL in CRM (mapped fields from BDOC to BAPI structures)
5. In the above note, for R/3 BAPI to R/3 API they have given to implement user exit USEREXIT_MOVE_FIELD_TO_VBAP which we found in MV45AFZZ. But in this we are unable to find BAPI Structure to map.
Our issue is, when a sales order is created in CRM, it is getting replicated on ECC. But, only standard fields are getting replicated. The custom fields that we have added are remaining empty on ECC side.
In CRM --> txn SMW01, we can see that the BDOC is populated with custom fields also.
Could you let us know if your issue is solved completely. Are you able to see the value of custom field, in ECC? Did you use AET to add fields in CRM.
Could you please give us the steps that you have done.

What are step involved in intercompany sale order

can any one tell me step by step process thank in advance ....

Refer the following metaling notes for detailed setup instructions of Internal requisition and Internal sales orders:
Internal Sales Order Cycle In Order Management [ID 744481.1]
Vision Demo - How To Create And Demonstrate The Internal Requisition To Internal Sales Order Flow [ID 1082223.1]
Hope that helps.
Pubs

How to replace TLB order in APO (/sapapo/snptlb) with external number

Hi All,
I am trying to replace TLB order (ex. APO-0001) created in transaction /sapapo/snptlb with an external number generated by me
(ex. test-123). Can anyone suggest an FM or anymethod or process for the same.
Win full points by answering this simple question !!
Thanks - Chandan

Dear Chandan
You can make the settings in SPRO->APO->SNP->Basic setting-> Maintain Number Ranges for orders . Maintain the number ranage and Tick it as External.
When you Run TLB, You can provide the external number.

What are the step to Cancel the iStore order hold

Hi All,
What are the steps to cancel the Order hold option in iStore, and OM all the orders for all user getting hold, Please tell me what are the steps to Cancel this hold option.
Thanks
Vivek

like below i set the profile options
ASO: Credit Card Authorization = No
ASO: Default Order State profile = Booked
IBE: Perform Payment authorization = Yes
and i removed the OM>> Customer >> standard >> credit Check option then also i am getting the same hold issue.
Your order is on "Hold" with Order Number 17968
Please print this page and keep it for your records. If you are faxing your credit card number or purchase order, remember to complete the Faxed Order section below before faxing.
Thanks
Vivek

Unable to see demand history in APO SPP via transaction /SAPAPO/SPPMDH

Hello
We are trying to view aggregated sales history data in APO SPP via transaction /SAPAPO/SPPMDH
We have loaded sales order data from flat file into DSO 9ARAWDAT & infocube 9ADEMAND. We can see the data in the cubes & also via the standard queries attached to 9ADEMAND cube.
Also we are able to adjust sales order item level data via transaction /SAPAPO/SPPMRD: Adjust Raw Data .
However we are unable to see any data when we try to adjust aggregated demand history via transaction /SAPAPO/SPPMDH.
The replenishment indicator is stocked & the forecast periodicity is maintained as well.
Could you please let us know if anything is missing? Thanks in advance

Santanu Paul wrote:
Hello
>
> We are trying to view aggregated sales history data in APO SPP via transaction /SAPAPO/SPPMDH
>
> We have loaded sales order data from flat file into DSO 9ARAWDAT & infocube 9ADEMAND. We can see the data in the cubes & also via the standard queries attached to 9ADEMAND cube.
>
> Also we are able to adjust sales order item level data via transaction /SAPAPO/SPPMRD: Adjust Raw Data .
>
> However we are unable to see any data when we try to adjust aggregated demand history via transaction /SAPAPO/SPPMDH.
>
> The replenishment indicator is stocked & the forecast periodicity is maintained as well.
>
> Could you please let us know if anything is missing? Thanks in advance
Hello,
Check this stuff (from help.sap.com) we had a quite similar issue, until we've fixed it:
For the demand categories we defined to be in your system, you have transferred the DataSources 9ADEM_CAT and 9ADEM_CAT_TXT as well as InfoSources 9ADEM_CAT and 9ADEM_CAT_TXT to the Business intelligence system (BI system) in SAP SCM and activated them. You have transferred the following InfoPackages for these InfoSources:
● Load Master Data from APO
● Load Texts for Demand Categories from APO
Note
Each time you change the relevant for forecast indicator of a demand category, you have to reactivate the master data of characteristic 9ADEM_CAT.

What are the roles in CRM implementation Project(all generic extractions)

Hi Gurus,
Now I am placed from a support project from BW (CRM) implementation project(all are generic extractions).
& I am also new to implementation project.
what are the neccessary steps to be taken when we are implementing BW for CRM.
Gurus please clarify my doubts.
1. what are the steps in implementation project in detail(as a developer).
2. what are the sizes of the cubes,ODS & How to decide them.
3. what are the neccessary steps for Master data & Transaction data.
4.How to make the functional specifications for Infoobjects,cubes,ODS,Remote cubes,Multiproviders.
5.can we change to delta loads to full loads if yes what happens to existing data.
6.How flat file extraction used in the case of crm& how to do ascii format.
7.What are the steps to be taken when we are creating Queries & Reports in BW CRM.
It's very urgent.
thanks = points.
Bwcheta.

1. what are the steps in implementation project in detail(as a developer).
U have to basically to the techinal design after understnading the functional designs and implemnet the same( creating infoobjects, datatargets, datasources, queries etc.). Then u have to load data and do the unit testing on the same.
2. what are the sizes of the cubes,ODS & How to decide them.
Completely the business reqmnet and the data that the client wants to load.
3. what are the neccessary steps for Master data & Transaction data.
U have to understand ur master data and transaction data on the basis of whch u have create ur infoobjects and load data in them and finally in the datatarget.
4. can we change to delta loads to full loads if yes what happens to existing data.
Sure u can do that by choosing Full update in the infopkg. It will just load the complete data instead of changed records.
*Hope it helps.

Sales orders ONLY in APO and not in R/3

Dear Friends,
I have this peculiar but very critical problem wherein:
APO creates an extra schedule line to an ALREADY EXISTING sales order only in APO with a quantity in decimals like 130.320 PCs or whatever. Also, important to note is that this line has a required date very much in the future starting from 12-2009. Also, this sales order schedule line is non existent in R/3!
- I have checked the R/3 SD tables but nothing which relates to this qty.
- I have checked the sales order changes, but nothing in the history which suggests that someone might have changed it.
- I checked the UOM both in R/3 & APO but nothing.
Now, the problem is that:
How & what created this sales order?
If it is in APO, then y it isnt being sent to R/3 like all the other normal sales orders?
Most critical: APO sees this reqt & automatically creates a planned order (bckgrnd) which is then sent to R/3 as a recpt!!
Thanks in advance !

Team Eusap,
You say you ran LC consistency (which would be /SAPAPO/OM17). Did you also run CCR as I mentioned earlier?
Although there are no Queue errors, it is possible that someone has deleted the item from the queue. So, continue.
You can try to delete the order in APO using program /SAPAPO/SDORDER_DEL. Select Delete on database tab, deselect test, select the appropriate product/location(S). Select 'without check'. Select both boxes in Additional functions. Since you are not using GATP, you are not using allocations, but it is OK to select these items too. Execute. Stay away from the 'Delete all DB Sales order Data" tab!, or you may have to re-cif all your orders across. Now redo your LC consistency.
As far as your models are concerned, you need to assure yourself that there are no ATP (transactional, not material independent) models open. Use CFM5 to search.
As for the material independent CIF, it is a good idea to inactivate this model after the initial transfer. If you ever do any ATP config within APO, this model can overwrite some of the settings you created in APO. Usually this is undesirable.
Let me know if any of the above steps allow you to delete the APO order you don't want.
Rgds,
DB49

Deletion of production order in ECC / APO

Hi,
It is not possible to set DLFL (Deletion flag) when the order is in
CRTD status also when the order is DLV or TECO with no actual cost or open order value .
It is happening in both the scenarios when
1. Plan order is created in APO and then converted to prod order
2. Plan order and prod order both are created in ECC , but both are transferred to APO
What shall be the process for deleting the prod order in ECC.
With regards,
Mrinal

Hi Mrinal,
1) You can delete the production order in created status in APO using transaction /n/sapapo/rlcdel, select the required categories for deletion.
Once the order gets deleted in APO, it will get deleted automatically from ECC also. If not the transaction /sapapo/ccr to be used which will remove it upon iteration.
2) Alternatively, if you carry out techo in ECC for a production order which is released, once after delting in ECC, queues needs to be cleared and then subsequently /sapapo/ccr to be run for production orders, so that it will get cleared from APO also upon iteration.
Please try these and let me know whether your query is resolved.
Regards
R. Senthil Mareeswaran.

What are the prerequisites for GATP and how to check SO in APO

Hi
I've created a Sales order in R/3. for this the availability check is being done in APO(SCM). when I press enter it is going to APO(SCM).
now i want to see this Sales order in APO(SCM), what is transaction for this? and do i need to maintain any CIF model to see the Sales order in APO.
pls give me some note on this.
thanx in advance
Satya
Edited by: Wilian Segatto on Jan 25, 2010 4:40 PM

Hello,
Please refer Building block of GATP, you will able to get systimatic way how to use GATP functionality in R/3 and APO as well as what are the settings require for it.
http://help.sap.com/bp_scmv150/BBLibrary/documentation/ATP_BB_ConfigGuide_EN_DE.doc

What are APO orders in APO (APO Order transaction:-SAPAPO/SNPTLB)?

Similar Messages

Maybe you are looking for