Daily Archives: August 18, 2007

Strategy group

SAP has predefined the following strategy groups:

  • 83: Assembly processing with network, account assignment category E (assignment to sales document. A network with network type PS05 (header assignment) is created.
  • 85: Assembly processing with network/project, account assignment category D (assignment to project). A network with network type PS04 (activity assignment) is created.

In both cases, the system automatically creates a network with network type PS04.

Recommendation

Do not change the default settings that SAP provides in Customizing. You can use these defaults to set up your own strategy groups, requirement types etc. and specify other network types or other settings for the availability check.

Note

  • When values are missing from the sales order item, such as the plant, the system cannot determine the requirements type which means that it also cannot create a network from the sales order.
  • In order to have the scheduled dates in the network be copied into the sales document as confirmed dates, you must have maintained scheduling parameters for network type PS04 and PS05 in Customizing.

Keep this in mind when you define your own network types.

  • Among the scheduling parameters to be maintained, you should set the indicator reconcile basic dates.

You must set this indicator if you want the system to copy the scheduled dates into the basic dates and then pass them on to the sales order as confirmed dates.

Advertisements

Useful Tcodes

Customer

        XD01    Create Customer (Centrally)

        XD02    Change Customer (Centrally)

        XD03    Display Customer (Centrally)

        XD04    Customer Changes (Centrally)

        XD05    Block customer (centrally)

        XD06    Mark customer for deletion (centr.)

        XD07    Change Customer Account Group

        XD99    Customer master mass maintenance

        XDN1    Maintain Number Ranges (Customer)

Vendor

        XEIP    Number range maintenance: EXPIMP

        XK01    Create vendor (centrally)

        XK02    Change vendor (centrally)

        XK03    Display vendor (centrally)

        XK04    Vendor Changes (Centrally)

        XK05    Block Vendor (Centrally)

        XK06    Mark vendor for deletion (centrally)

        XK07    Change vendor account group

Sales Order

        VA00    Initial Sales Menu

        VA01    Create Sales Order

        VA02    Change Sales Order

        VA03    Display Sales Order

        VA05    List of Sales Orders

        VA07    Compare Sales - Purchasing (Order)

        VA08    Compare Sales - Purchasing (Org.Dt.)

Inquiry

        VA11    Create Inquiry

        VA12    Change Inquiry

        VA13    Display Inquiry

        VA14L   Sales Documents Blocked for Delivery

        VA15    Inquiries List

Quotation

        VA21    Create Quotation

        VA22    Change Quotation

        VA23    Display Quotation

        VA25    Quotations List

        VA26    Collective Processing for Quotations

Contract

        VA41    Create Contract

        VA42    Change Contract

        VA42W   Workflow for master contract

        VA43    Display Contract

        VA44    Actual Overhead: Sales Order

        VA45    List of Contracts

        VA46    Coll.Subseq.Processing f.Contracts

Item Proposal

        VA51    Create Item Proposal

        VA52    Change Item Proposal

        VA53    Display Item Proposal

        VA55    List of Item Proposals

        VA88    Actual Settlement: Sales Orders

Delivery (Outbound)

        VL00    Shipping

        VL01    Create Delivery

        VL01N   Create Outbound Dlv. with Order Ref.

        VL01NO  Create Outbound Dlv. w/o Order Ref.

        VL02    Change Outbound Delivery

        VL02N   Change Outbound Delivery

        VL03    Display Outbound Delivery

        VL03N   Display Outbound Delivery

        VL04    Process Delivery Due List

        VL06    Delivery Monitor

        VL06C   List Outbound Dlvs for Confirmation

        VL06D   Outbound Deliveries for Distribution

        VL06F   General delivery list - Outb.deliv.

        VL06G   List of Oubound Dlvs for Goods Issue

        VL06I   Inbound Delivery Monitor

        VL06IC  Confirmation of putaway inb. deliv.

        VL06ID  Inbound Deliveries for Distribution

        VL06IF  Selection inbound deliveries

        VL06IG  Inbound deliveries for goods receipt

        VL06IP  Inbound deliveries for putaway

        VL06L   Outbound Deliveries to be Loaded

        VL06O   Outbound Delivery Monitor

        VL06P   List of Outbound Dlvs for Picking

        VL06T   List Outbound Dlvs (Trans. Planning)

        VL06U   List of Uncheckd Outbound Deliveries

        VL08    Confirmation of Picking Request

        VL09    Cancel Goods Issue for Delivery Note

        VL10    Edit User-specific Delivery List

        VL10A   Sales Orders Due for Delivery

        VL10B   Purchase Orders Due for Delivery

Customer management

        FD01    Create Customer (Accounting)

        FD02    Change Customer (Accounting)

        FD02CORE        Maintain customer

        FD03    Display Customer (Accounting)

        FD04    Customer Changes (Accounting)

        FD05    Block Customer (Accounting)

        FD06    Mark Customer for Deletion (Acctng)

        FD08    Confirm Customer Individually(Actng)

        FD09    Confirm Customer List (Accounting)

        FD10    Customer Account Balance

        FD10N   Customer Balance Display

        FD10NA  Customer Bal. Display with Worklist

        FD10NET Customer Balance Display

        FD11    Customer Account Analysis

        FD15    Transfer customer changes: send

        FD16    Transfer customer changes: receive

        FD24    Credit Limit Changes

        FD32    Change Customer Credit Management

        FD33    Display Customer Credit Management

        FD37    Credit Management Mass Change

Pricing

        V/03    Create Condition Table (SD Price)

        V/04    Change Condition Table (Sales pr.)

        V/05    Display Condition Table: (Sales Pr.)

        V/06    Condition Categories: SD Pricing

        V/07    Maintain Access (Sales Price)

        V/08    Conditions: Procedure for A V

        V/09    Condition Types: Account Determin.

        V/10    Account Determination: Access Seqnc

        V/11    Conditions: Account Determin.Proced.

        V/12    Account Determination: Create Table

        V/13    Account Determination: Change Table

        V/14    Account Determination: Display Table

BOM

        CS00    BOM Menu

        CS01    Create Material BOM

        CS02    Change Material BOM

        CS03    Display Material BOM

        CS05    Change Material BOM Group

        CS06    Display Material BOM Group

        CS07    Allocate Material BOM to Plant

        CS08    Change Material BOM - Plant Alloc.

        CS09    Display Allocations to Plant

        CS11    Display BOM Level by Level

        CS12    Multilevel BOM

        CS13    Summarized BOM

        CS14    BOM Comparison

        CS15    Single-Level Where-Used List

        CS20    Mass Change: Initial Screen

        CS21    Mass Material Change: Initial Screen

        CS22    Mass Document Change: Initial Screen

        CS23    Mass Class Change: Initial Screen

        CS25    Archiving for BOMs

        CS26    BOM deletion

        CS27    Retrieval of BOMs

        CS28    Archiving for BOMs

        CS31    Create class BOM

        CS32    Change class BOM

        CS33    Display class BOM

        CS40    Create Link to Configurable Material

        CS41    Change Material Config. Allocation

        CS42    Display Material Config. Assignment

        CS51    Create standard BOM

        CS52    Change standard BOM

        CS53    Display standard BOM

        CS61    Create Order BOM

        CS62    Change Order BOM

        CS63    Display Order BOM

        CS71    Create WBS BOM

        CS72    Change WBS BOM

        CS73    Display WBS BOM

        CS74    Create multi-level WBS BOM

        CS75    Change multi-level WBS BOM

        CS76    Display multi-level WBS BOM

        CS80    Change Documents for Material BOM

        CS81    Change Documents for Standard BOM

        CS82    Change documents for sales order BOM

        CS83    Change documents for WBS BOM

        CS84    Change documents for class BOM

        CS90    Material BOM Number Ranges

        CS91    Number Ranges for Standard BOMs

        CS92    Number Ranges for Sales Order BOMs

 

Reports

Go to t-code SARP and select SD01 as a reporting Key. You will get
reporting menu tree for SD. All LIS reports are standard SD and logistics reports. Any report starting with “MC**” will be a standard LIS report. e.g. MCSI,MCTG, MCTE etc.

Create a Query

Procedure:
1. go to SQ03 – Create a User grp with ZSAMBIT
2. go to SQ02 – Create a Infoset – 2 options 1. logical database for general output and if u want a customized output then go for table joins.
Start with specifying a table name like VBAP and further joins other tables which has common field links like how ABAPers join tables for the Report.(Provided u know the technical)
3. Again go to SQ03 – Click on assign user & infoset, here u can assign SAP User ID so that those users can view or change ur query and also u need to assign the infoset u hve created in SQ02.
4. SQ01 create a Query – choose the User grp and here u can choose the fields depending on the list u want in your report

Assign more than 999 Ship-to’s to a Sold to party

Due to the 999 entry restriction we cannot maintain more than 999 ship to party in the sold to customer master data, to overcome this problem we have implemented a workaround, We don’t maintain the ship to party in the sold to party customer data , but we maintain the sold to party in the Ship to customer master data. Hence while entering the Sales order, business is supposed to enter the ship to party field and we expect the sold to party to be determined. This doesn’t happen in the standard way so our plan is to use the partner determination user exit to get the Sold to party master data. I understand that in order to use the partner determination user exit EXIT_SAPLV09A_003 we need to make some changes in the configuration of partner determination procedure as well (source X, Y or Z in partner determination procedure, transaction VOPA). Is there any other changes required which needs to be done.

User Exits for adding another field at header/item level

Basics of modification in pricing* The following communication structures are relevant in pricing:

– KOMK (pricing communication header)

– KOMP (pricing communication item)

– KOMG (allowed fields for condition structures)

For technical reasons, the communication structure KOMG is used, which
combines KOMK and KOMP, and which contains all fields which can
generally be used for pricing. When entering new fields in KOMK or KOMG,
the fields are automatically included in KOMG.

* Fields for pricing are integrated into the following INCLUDES:

– header data in KOMKAZ (INCLUDE in KOMK or in KOMG)

– item data in KOMPAZ (INCLUDE in KOMP or in KOMG)

* The routines for assigning values to the new fields in order
processing are found in member MV45AFZZ. Use the following user exits:

– USEREXIT_PRICING_PREPARE_TKOMK (header fields)

– USEREXIT_PRICING_PREPARE_TKOMP (item fields)

* The routines for assigning values to the new fields in billing
are found in member RV60AFZZ. Use the following user exits:

– USEREXIT_PRICING_PREPARE_TKOMK (header fields)

– USEREXIT_PRICING_PREPARE_TKOMP (item fields)

Examples for using new fields in pricing

Example 1

In the first example, parts of a document field are to be used in
pricing. You want to use the first three digits of the product hierarchy
(PRODH) for pricing, for example. Proceed as follows:

1. Check the data elements in the standard system.

2. Since there is no such data element you have to create the new
data element ZZPRODH1. Also create a domain with the length “3” and the
data type “CHAR” for the new data element.

Remember that new data fields must start with the letters “ZZ” or “YY”,
since SAP reserved these letters to protect them from being overwritten
during a release upgrade.

3. Check whether the product hierarchy (PRODH) is found at header
or at item level.

In table VBAP, document field PRODH is defined as an item field.

4. Integrate the field name ZZPRODH in the communication structure
KOMP using the INCLUDE KOMPAZ and allocate the data element PRODH to it.

5. Activate the structure.

6. Check in which table the field PRODH exists.

The field is in table VBAP (sales document: item data).

7. Assign a value to the new field in the FORM routines for sales
order processing and billing using the appropriate user exits:

In sales order processing the user exit is found in member MV45AFZZ. The
complete statement is:

FORM USEREXIT_PRICING_PREPARE_TKOMP.

MOVE VBAP-PRODH(3) TO TKOMP-ZZPRODH.

ENDFORM.

The routines for assigning a value to the new fields in billing are
found in member RV60AFZZ. The statement is as follows:

FORM USEREXIT_PRICING_PREPARE_TKOMK

MOVE VBRP-PRODH(3) TO TKOMP-ZZPRODH.

ENDFORM.

8. Allocate the specifications A, V and 001 to the field ZZPRODH in
table T681F.

Example 2

In the second example, you want to use a partner function for pricing
which was created in Customizing for partner maintenance.

Assume that the partner function was created for a sales representative
of the partner type PE. Z1 is defined as a mandatory function for the
customer master record, therefore automatically set in the document and
available in the internal partner table XVBPA.

To use the new partner function for pricing, proceed in the same way as
for the previous examples.

1. Create a new data element, in this example, the data element
ZZVRTZ1 with the domain PERNR.

2. Include the field ZZVRTZ in KOMK using KOMKAZ and allocate the
data element ZZVRTZ1 to it.

For order processing, assigning a value to the field is carried out in
the user exit for member MV45AFZZ. The entries in the user exits are
protected during a release upgrade. The statement is as follows:

FORM USEREXIT_PRICING_PREPARE_TKOMK.

PERFORM XVBPA_LESEN (SAPFV45K) USING ‘Z1’ VBAP-POSNR SY_TABIX.

MOVE XVBPA-PERNR TO TKOMK-ZZVRTZ