Correction of SD Document Status

---

1472007 - Document status has to be corrected

Reorganization of SD Document Index

Reorganization of SD Document Index

---

128947 - Correction of SD document indexes with RVV05IVB

[SD] Item Categories Assignment

項目類型的指派

This assignment is influenced by:

• Item categories are assigned to sales document types .
  Configure the system to propose an item category when you create an order.
• The item category group from the material master record.
  The item category group allows you to group together different materials that behave in a similar way during sales and distribution processes, for example. You can also define new item category groups if needed.
• The usage for the item , which in some cases is set internally in the program.
  The system uses TEXT if the user enters an item in the inquiry or quotation by entering data in the "Description" field without specifying a material number. FREE is used for controlling free goods items.

  
  

  Trace list:

  
  Function Module RV_VBAP_PSTYV_DETERMINE
  Include FV45CF0C_CVBAP_FUSSZEILE_PRUEF
  Subroutine CVBAP_FUSSZEILE_PRUEFEN
    Include FV45PF0V_VBAP-PSTYV_PRUEFEN
  
    Subroutine VBAP-PSTYV_PRUEFEN
  Include FV45PFAP_VBAP_FUELLEN
    Subroutine VBAP_FUELLEN
  Include FV45PFAP_VBAP_FUELLEN_AUART_CH
    Subroutine VBAP_FUELLEN_AUART_CHANGE
  
  
  Function Module WTAD_ADDIS_IN_SO_IDOC_SLS_DET
  

  
  
• The item category of a higher-level item (in the case of a sub-item)

[SD] Get accounting document for billing document

How to get accounting doc for billing doc?

---

You can use function: AC_DOCUMENT_RECORD

[BAPI] BAPI_CONTRACT_CREATEFROMDATA

使用 BAPI 建立 Contract

---

定義

* BAPI Define
  DATA: gw_so_header          LIKE bapisdhd1,
        gw_so_headerx         LIKE bapisdhd1x,
        gw_so_logic_switch    LIKE bapisdls,
        gv_so_doc_in          TYPE bapivbeln-vbeln,
        gv_so_doc_num         TYPE bapivbeln-vbeln,
        gt_so_return2         TYPE bapiret2,
        gt_so_partners        TYPE bapiparnr  OCCURS 0 WITH HEADER LINE,
        gt_so_items_in        TYPE bapisditm  OCCURS 0 WITH HEADER LINE,
        gt_so_items_inx       TYPE bapisditmx OCCURS 0 WITH HEADER LINE,
        gt_so_return1         TYPE bapiret2   OCCURS 0 WITH HEADER LINE,
        gt_so_conditions_in   TYPE bapicond   OCCURS 0 WITH HEADER LINE,
        gt_so_conditions_inx  TYPE bapicondx  OCCURS 0 WITH HEADER LINE.

夥伴功能

[Code] Bills of material in the BAPI for create SO

使用 BAPI 建立含 BOM 的銷售訂單，重點在於先使用 BAPI_SALESORDER_SIMULATE 算出所有的 item no, 另外就是呼叫 BAPI_SALESORDER_CREATEFROMDAT2 時要使用 Exporting 參數 int_number_assignment = 'X'

[BAPI] to create sales orders

BAPIs to create sales orders for Returns and Debit Memo Request
https://forums.sdn.sap.com/message.jspa?messageID=4222007

---

Hi,

I have to create a sales order for document type Returns as well as a debit memo request.The BAPI 'BAPI_SALESORDER_CREATEFROMDAT2' is giving the following error message for Debit Memo Request document creation as well as for Returns.

761 Unpermitted combination of business object BUS2032 and sales doc. category L

Getting Sales order -Schedule line field , Delivered Quantity ( VSMNG )

I need to use the Delivered Quantity present in a sales order at schedule line level.

Sheeba Bhaskaran

Posts:	252
Registered:	2/27/07
Forum Points:	302
Re:	Getting Sales order -Schedule line field , Delivered Quantity ( VSMNG ) ??
Posted:	Jan 13, 2009 10:38 AM
Content:	Hi. You can use the function module RV_SCHEDULE_CHECK_DELIVERIES to get the delivered quanity corresponding to schedule line item in sales order. Please refer below code: ie3mdpslx-delnr:   is sales order numer ie3mdpslx-delps:   is line item. internal table tl_da_vbep has got field VSMNG which is the delievred quantity for each line item SELECT * FROM vbfa INTO CORRESPONDING FIELDS OF TABLE tl_xvbfa WHERE vbelv = ie3mdpslx-delnr AND posnv = ie3mdpslx-delps AND vbtyp_v = 'C'. SELECT * FROM vbup INTO CORRESPONDING FIELDS OF TABLE tl_xvbup WHERE vbeln = ie3mdpslx-delnr AND posnr = ie3mdpslx-delps. SELECT * FROM vbep INTO CORRESPONDING FIELDS OF TABLE tl_da_vbep WHERE vbeln = ie3mdpslx-delnr AND posnr = ie3mdpslx-delps. SELECT * FROM vbap INTO CORRESPONDING FIELDS OF TABLE tl_xvbap WHERE vbeln = ie3mdpslx-delnr AND posnr = ie3mdpslx-delps. CALL FUNCTION 'RV_SCHEDULE_CHECK_DELIVERIES' EXPORTING fbeleg = ie3mdpslx-delnr fposnr = ie3mdpslx-delps TABLES fvbfa = tl_xvbfa fvbup = tl_xvbup fxvbep = tl_da_vbep fvbap = tl_xvbap EXCEPTIONS fehler_bei_lesen_fvbup = 1 fehler_bei_lesen_fxvbep = 2 OTHERS = 3.

[Link] Enhancements and Business add-ins used in standard t-codes of SD

Enhancements represent potential customer requirements that have not been developed in the standard software. Instead, the standard provides for further development of such exits at the customer site, using logic specific to the customer. Upward compatibility is assured since SAP guarantees that the call of an enhancement from the standard software and the calling interface will remain valid in future releases.

The link address is: http://wiki.sdn.sap.com/wiki/display/ERPLO/Enhancements+andBusiness+add-ins+used+in+standard+t-codes+of+SD

[Manual] SAP Retail

SAP Retail is a fully integrated, self-contained system comprising all the functions you require to model retail business processes. SAP Retail also includes general SAP components such as Financial Accounting, Controlling and Human Resources.

The link address is: http://help.sap.com/saphelp_erp60_sp/helpdata/en/12/084110470311d1894a0000e8323352/frameset.htm

[Link] Variant Configuration Overview

The link address is: http://www.slideshare.net/arun_bala1/variant-configuration-overview

[Link] SAP SD Sales Deal & promotion

The link address is: http://www.slideshare.net/arun_bala1/sap-sd-sales-deal-promotion

[Link] Sales Promotions

The link address is: http://www.slideshare.net/prahladk/sales-promotions-203140

[SD] Sales Deal

A sales deal defines a marketing deal for a certain product. Depending on the setting, it can be allocated to a higher-level promotion.

Special condition records can be allocated to a sales deal. If relevant, the records also contain the number of the promotion allocated to the sales deal.

The control of sales deals includes the following options in Customizing:

• Define agreement types for sales deals
  The agreement type indicates the type of the sales deal, for example, whether it refers to a product or product line. The standard system contains sales deal type 0020.
• Define and allocate condition type groups
  A condition type group defines a group of condition types and condition tables which can be used together in the sales deal. Using the condition type group, it is possible to deal with individual products differently in a sales deal and, for example, to grant discounts specific to a customer or material.

Actions

Proceed as follows to define your own sales deals:

1. Create an agreement type by specifying a numeric key with a maximum of four digits and a description for the agreement type.
2. Specify the different control data on the detail screen of the agreement type (for example, validity period as default value, overview screen). In the agreement hierarchy, specify whether an allocation to a promotion may, can or must be made.
3. (Empty?)
4. Note
5. Further down in the Pricing chapter in Overviews you can also select a certain overview for sales deals as the default screen for maintenance of master data. For example, you can define an overview that should only be displayed for maintaining payment conditions for certain condition records.

[SD] Promotion

A promotion is a marketing plan for a certain product line (for example, during the market launch).

A promotion can be made up of several sales deals.

In Customizing, you have the following options for controlling promotions:

• Define promotion type
• Set up number ranges for promotions, if necessary
  The same number range is used for promotions as in rebate processing. If you want to use separate number ranges, make the appropriate setting.
• Enter the overview screen displayed for the user to create master data

Note

The same authorization object is used for promotions as for rebate processing (V_KONA_VKO).

Actions

1. Enter a numeric key with a maximum of four digits and a description for the promotion type.
2. On the detail screen, specify control data, such as:
   • Agreement category "P" for promotion
   • Validity period proposed as a default value
   • Overview screen
3. If necessary, create new number ranges (internal or external).

Transport

You transport number range objects as follows:

Choose Interval -> Transport in the accounting document Number Range screen.

All intervals for the selected number range object are deleted in the target system first. After the import, only the intervals you export are present. The number statuses are imported with their values at the time of export.

Dependent tables are not transported or converted.

[Manual] Sales (SD-SLS)

Sales allows you to execute different business transactions based on sales documents defined in the system.

The link address is: http://help.sap.com/saphelp_erp60_sp/helpdata/en/dd/55fa7a545a11d1a7020000e829fd11/frameset.htm

[SD] Package - VREP

Application development RV reporting

Programs:

• RV50SBT1 (VL04)
  銷售訂單 / 採購單工作單：選擇
• RV75FGR0
  銷售文件關聯圖
• RVKUSTA1
  銷售彙總
  使用 Logical DB SD_KUSTA
• RVSCD100
  顯示文件變更(訂單)
• RVSCD200
  顯示文件變更(訂單，不同的選項和輸出)
• RVSCD300
  顯示文件變更(請款文件)
• SAPMV62S
  交貨彙總處理（交貨到期清單）

---

Other Reports:

• RVV05T01 Display Order Items for the Material
• SDORDE01 Orders within time period
• RKKBALV1 Order Selection
• RV50SBT1 Sales orders/purchase orders worklist: Selection

[SD] User Exits For Billing

• USEREXIT_NUMBER_RANGE (Module pool SAPLV60A, program RV60AFZZ)
  The internal number range used in the standard system is specified in the billing type table and can be changed in this user exit. This user exit is only called when the billing documents is created.
• USEREXIT_ACCOUNT_PREP_KOMKCV (Module pool SAPLV60A, program RV60AFZZ)
  In this user exit additional fields for account determination that are not provided in the standard system are copied into communication structure KOMKCV (header fields).
• USEREXIT_ACCOUNT_PREP_KOMPCV (Module pool SAPLV60A)
  In this user exit additional fields for account determination that are not provided in the standard system are copied into communication structure KOMPCV (item fields).
• USEREXIT_NUMBER_RANGE_INV_DATE (Module pool SAPLV60A, program RV60AFZC)
  Depending on the number range, table TVFKD is used to set the billing date (country-specific requirments in Italy). USEREXIT_NUMBER_RANGE is automatically deactivated when this user exit is being applied.
• USEREXIT_FILL_VBRK_VBRP (Module pool SAPLV60A, program RV60AFZC)
  This user exit is only called when the billing document is created. It is used to provide the header and the item of the new billing document with deviating or additional data.
• USEREXIT_PRINT_ITEM (Module pool SAPLV61A, program RV61AFZB)
  Printing the item line of a billing document can be supplemented or changed.
• USEREXIT_PRINT_HEAD (Modulpool SAPLV61A, Programm RV61AFZB)
  Printing the header line of a billing document can be supplemented or changed.
• User exits in program RV60AFZD
  Short descriptions of the user exits are contained in the program:
  • USEREXIT_RELI_XVBPAK_AVBPAK
  • USEREXIT_NEWROLE_XVBPAK_AVBPAK
  • USEREXIT_NEWROLE_XVBPAP_AVBPAK

The following user exits are available in report SAPLV60B for transfer to accounting (function group V60B):

• EXIT_SAPLV60B_001: Change the header data in the structure acchd
  You can use this exit to influence the header information of the accounting document. For example, you can change the business transaction, "created on" date and time, the name of the person who created it or the transaction with which the document was created.
• EXIT_SAPLV60B_002: Change the customer line ACCIT
  You can use this exit to change the customer line in the accounting document. This exit is processed once the ACCIT structure is filled in with data from document header VBRK.
• EXIT_SAPLV60B_003: Change the customer line in costing
  The customer line is filled in differently for costing. You can use exit 003 to influence the ACCIT structure.
• EXIT_SAPLV60B_004: Change a GL account item ACCIT You can add information to a GL account item (such as quantity specifications) with this exit.
• EXIT_SAPLV60B_005: User exit for accruals
  Once all relevant data for accruals was entered in the GL account item, you can add to this data with this exit.
• EXIT_SAPLV60B_006: Change the control line ACCIT
  You can use exit 006 to add information to the control line.
• EXIT_SAPLV60B_007: Change the installment plan (Enhancement: SDVFX007)
  You can use exit 007 to add information to the installment plan
  parameters in the GL account item.
• EXIT_SAPLV60B_008: Change the transfer structure ACCCR, ACCIT and ACCHD (Enhancement: SDVFX008)
  After the accounting document is filled in with data, you can use exit 008 to change the document once again.
  Example Code:

  *&---------------------------------------------------------------------*
  *&  INCLUDE           ZXVVFU08                                         *
  *&---------------------------------------------------------------------*
  CHECK CVBRK-KALSM = 'Z001'.
  CHECK CVBRK-VKORG = '1000' OR
        CVBRK-VKORG = '2000'.
  LOOP AT CVBRP.
    CHECK CVBRP-MATNR(2) = 'XX'.
    READ TABLE XACCIT WITH KEY PAOBJNR = CVBRP-PAOBJNR.
    CHECK SY-SUBRC = 0.
    XACCIT-SGTXT = CVBRP-ARKTX.
    MODIFY XACCIT INDEX SY-TABIX.
  ENDLOOP.
  

• EXIT_SAPLV60B_010: Item table for customer lines (Enhancement: SDVFX010)
  You can use exit 10 to influence the contents of customer lines before they are created.
• EXIT_SAPLV60B_0011: Change the parameter for cash account determination or reconciliation account determination (Enhancement: SDVFX011)
  You can use this exit to change inbound parameters in order to influence account determination.

[SD] User Exits For Credit Checks And Risk Management

Credit Check

If you want to carry out your own individual credit checks, that differ from those in the standard system, you must define them in the following user exits:

• LVKMPTZZ
• LVKMPFZ1: USER_CREDIT_CHECK1
• LVKMPFZ2: USER_CREDIT_CHECK2
• LVKMPFZ3: USER_CREDIT_CHECK3

User exit for availability check

User exit USEREXIT_AVAIL_CHECK_CREDIT exists in Include MV45AFZF.

This user exit allows you to determine whether the system should or should not carry out an availability check after a blocked document has been released or after a new credit check.

Risk Management for Receivables

• RVKMPUS2
  Using this user exit, you can define new forms of payment guarantee.

[SD] User Exits For Price Determination

• USEREXIT_PRICING_PREPARE_TKOMK (module pool SAPLV60A, program RV60AFZZ)
  This user exit allows you to copy additional fields for pricing in the TKOMK communication structure (header fields), which have not been provided in the standard SAP system. These fields can also be used for pricing in the billing document.
  This user exit is described in detail in the "New fields in pricing" section.
• USEREXIT_PRICING_PREPARE_TKOMP (module pool SAPLV60A, program RV60AFZZ)
  This user exit allows you to copy additional fields for pricing in the TKOMP communication structure (item fields), which have not been provided in the standard SAP system. These fields can also be used for pricing.
  This user exit is described in detail in the "New fields in pricing" section.
• USEREXIT_FIELD_MODIFICATION (module pool SAPMV61A, program MV61AFZA)
  You can use this user exit to adjust the display of individual lines in the condition screen by changing the display attributes of the screen fields. This does not include the display of subtotals.
  This user exit is also used in order processing.
• USEREXIT_FIELD_MODIFIC_KZWI (module pool SAPMV61A, program MV61AFZB)
  You can change the display of subtotals in the condition screen by changing the display attributes of the screen fields.
  This user exit is also used in order processing.
• USEREXIT_FIELD_MODIFIC_KOPF (module pool SAPMV61A, program MV61AFZB)
  You can adjust the display of subtotals in the condition screen to your requirements by changing the display attributes of the screen fields.
  This user exit is also used in order processing.
• USEREXIT_FIELD_MODIFIC_LEER (module pool SAPMV61A, program MV61AFZB)
  You can adjust the display of blank lines in the condition screen to your requirements by changing the display attributes of the screen fields.
  This user exit is also used in order processing.
• USEREXIT_PRICING_CHECK (module pool SAPMV61, program MV61AFZA)
  You can install additional checks to the standard checks of condition lines (e.g. maximum/minimum value).
• USEREXIT_PRICING_RULE (module pool SAPLV61A, program RV61AFZA)
  In the standard SAP system, it is predefined which condition categories and classes can be copied or recalculated per pricing type. You can change the predefined standard procedure for each pricing type.
• USEREXIT_CHANGE_PRICING_RULE (module pool SAPMV61A, program MV61AFZA)
  You can use this user exit to change the pricing type that has been predefined in the copying control table in billing.
• USEREXIT_XKOMV_BEWERTEN_INIT (module pool SAPLV61A, program RV61AFZB)
  This field is used in the formulas and therefore initialized before the loop for the pricing procedure starts.
• USEREXIT_XKOMV_BEWERTEN_END (module pool SAPLV61A, program RV61AFZB)
  Within a loop for the price components during pricing, specific values can be transferred into the communication structures in pricing to be further processed.
• USEREXIT_XKOMV_ERGAENZEN (module pool SAPLV61A, program RV61AFZB)
  In change mode, you can change the dynamic part of the condition record (KONVD) that is always redetermined (i.e. it is not stored in database table KONV).
• USEREXIT_XKOMV_ERGAENZEN_MANU (module pool SAPLV61A, program RV61AFZB)
  You can use this user exit to change the ready-for-input fields of the manually entered condition record in add mode in the condition screen.
• USEREXIT_XKOMV_FUELLEN (module pool SAPLV61A, program RV61AFZB)
  This user exit is always called up during a redetermination of all or individual price components. You can change the work fields of the condition line. However, this only applies to conditions that have been determined via a condition record.
• USEREXIT_XKOMV_FUELLEN_O_KONP (module pool SAPLV61A, program RV61AFZB)
  This user exit is always called up during a redetermination of all or individual price components. You can change the work fields of the condition line. However, this only applies to conditions that have been determined via a condition record. This may include subtotals, manually entered conditions or conditions that have been calculated with a formula.
• USEREXIT_PRICING_COPY (module pool SAPLV61A, program RV61AFZA)
  You can change the KONV fields for copied price components.