SAP SD Forum

SAP SD Practice Projects

2009-02-10T14:40:00.000-08:00

Hello,

The idea behind this page is to help those consultants who have acquired SAP skills through training or self studies but have not yet been able to find projects where they could apply their knowledge and gain confidence therefrom.

For those of you, who are interested in getting these projects, first read the details below and then email me at jd@sapsdforum.com with your specific requirement (simple / medium or complex).

These projects are categorized broadly in these 3 categories depending on the complexity level. This will help you choose the best project as per your needs.

	Simple	Medium	Complex
Sales areas	2	5	10
Standard sales	Y	Y	Y
Return sales	Y	Y	Y
Customer Master	Y	Y	Y
Account determination	Y	Y	Y
Material determination	Y	Y	Y
Material listing/ exclusion	Y	Y	Y
Pricing	Y	Y	Y
Text		Y	Y
Customer Material Info		Y	Y
Intercompany Pricing		Y	Y
Consignments		Y	Y
Scrap sales		Y	Y
Intrecompany Sales		Y	Y
Sales BOM		Y	Y
Credit limits		Y	Y
Customer blocking		Y	Y
Posting Material stock		Y	Y
Functional Specs	1	4	8
Business Process Procedures	2	6	12
Test Scripts	2	6	12
3rd party sales			Y
Variant Configuration			Y
Credit Card Payment			Y
Down Payment			Y
Invoice Retention			Y
Rebate			Y
Product Hierarchy			Y
EDI/IDOC			Y
Condition Exclusion			Y
Supplementary Conditions			Y
*Charges - Blueprint Only*	*USD 200,-*	*USD 250,-*	*USD 300,-*
*Charges - Complete solution*	*USD 400,-*	*USD 500,-*	*USD 650,-*

Here are the terms for order processing -
1. 50% of the total order value payable in advance through paypal (www.paypal.com). My ID with paypal is -jitesh.dua@gmail.com.
2. Within 7 days of receipt of payment, you will receive the blueprint document including the complete gap analysis. In case within these 7 days, for any reason, you decide to cancel the order, you may do so with full refund of your money.
3. Whenever you are ready to get the solution (project plan, configuration document and the Functional Specifications), you may send the remaining 50% through the same channel (paypal).
4. You will receive the requested documents within 7 days of receipt of the payment.
5. You will be entitled to follow-on support (through email) for 15 days after the complete solution is mailed to you.
What will I provide - I will be providing a word document which specifies the requirements. In SAP terms , the AS-IS part of blueprint document and depending on your requirements - any or all of the following documents as well.

What you need to do - You would need to have access to an IDES /SAP Demo system and need to get the basic configuration from other modules (FI and MM). This will be the flow of activities afterwards -

1. Completing the blueprint - This will involve finding out what all can be done using standard SAP functions and for which scenarios would you need developments (Gaps). You will prepare a time line or a project plan and assign deadlines to each task and clearly marking the dependencies on other tasks.

2. Implementation -In this phase you will start configuring your SAP system in line with the requirement and as per the project plan.

3. Development - Here you will start developing functional specifications for development objects. The development objects include Reports, Interface, Conversions, Enhancements and Forms (RICEF). In the functional specification, you will identify the table and field name from where you will get the data and also write the logic to get data from multiple tables.

4. Testing - Once these objects are developed, they need to be tested (I am not sure if you would have any ABAPper to develop these objects for you)

5. Documentation - In this phase you will be preparing the following documents - BPP (business Process Procedures) and CD (Configuration documents) and Test Scripts.

If you are interested in buying but wondering how it will look like, mail me at jd@sapsdforum.com for a free sample.

thanks

Jitesh

Steps for Variant Configuration and Pricing

2007-10-26T07:10:00.000-07:00

1. Create a Material of your Motor Cycle using Material type KMAT(MM01).

2.Then create a characteristic called ZColour(SAP has a standard Characteristic for this but it has multiple values-i.e you can select more than one colour for your Bike.If you do not want that create your own)with character format and assign single value radio button on the initial screen. Go to values Tab and give the colors you need.save the characteristic. Similarly repeat for CC (I figure this CC as 100cc & 200cc kind of thing. If you want these as materials then it is a different story-I am taking this as feature as well)

3. Create a class called Zbike with the above 2 characteristics and save the class.

4. Create a configuration profile Zbikeprof using Cu41 and assign the Kmat material to Class Zbike,

5. Then create the order and Enter the Kmat material you want in the Order.

————————————-
Q - In variant configuration I have configured my material properly during sales order creation it is selecting proper characterstics but my question is pricing should calculate at characterstics level not at header level.

————————————
A - Pricing in variant Configuration is done at the Header level only. The logic is that you create pricing variant keys for each characteristic Value. This will be done at the Header level using cond type VA00.based on the characteristic chosen the appropriate price according to the pricing variant key will be picked up.

————————————-
Q - Here my question is with out creating the materials is it possible to get price based on the characterstics.

I am working on variant configuration here my product is 9-100. i have created characterstics for describing colours. this characterstics assigned to class, this class is assigned to 9-100(KMAT type). here i have not created amterial to describe each colour.

Now how I need to setup my system to calculate the price based on colour.

————————————-
A - A cool Question. It will really get us into the thick of things in Variant Configuration.

Here are the steps.

1. Create a Characteristic called ZColour(Standard SAP has a characteristic called colour.I did not use it.)
Give your values.
Say, Red & Blue

2. Now create another characteristic called ZCol_surcharge
Give the description and go directly to Addnl Data Tab.Here in the table name Enter “SDCOM” and in the Field Name Enter “VKOND”.The system will pick up the format from the Dictionary.

3. Now go to CT04 and change the Characteristic Zcolour.
Go to values tab and select RED.Goto Extras-> Object Dependencies->Editor and then select Procedure.

In front of 000010 Enter $self.ZCol_surcharge=’RED’.
Similarly Select Blue and enter $self.ZCol_surcharge=’BLUE’

3. Link both these characteristics to the Class(The class which you have attached the KMAT Material).

4. Go to VK11 and the Enter VA00.Then give the values RED and BLUE and enter the values.

5. Go to your order and Enter your material.

————————————-
Q - Here are some clarifications required from you.

what is the significance of item category group 0002 and 0004. Apart from these are they any other item category groups are available for configurable materials ?
In BOM header material having components. is it possible to make the component as configurable material.

————————————-
A - The difference b/w 0002 and 0004 is basically that of LUMF & ERLA.
In 0002 the pricing happens at the Header Item Level.
In 0004 the pricing happens at the Sub Item Level.
Check out the Item category Assignments and things will be Clear.

I think these two are the only ones used for Configuration.

Please let me know in which Scenario you would like to have the configurable material Inside a BOM(as it would help me in visualising thh Item Category Assignment).

————————————-
Q - As you said I setup my system to calculate price based on colour.
ZCOLOUR contains all colours in values tab page.
ZPRICE contains table name and filed name in additional data tab page.

I went to ZCOLOUR characterstics I maintained (extras-object dependicies-editor-action) there I have given $self.ZPRICE = ‘RED’ for all the values.

when am creating the sales order price is coming only for RED colour not other colours. even price is maintained for all the colours.

————————————-
A - Seems like there is a mistake in the line $self.ZPRICE = ‘RED’ (You have said you have given this for all the values- If I have not mistaken). This refers only to red colour.

In front of 000010 Enter $self.ZCol_surcharge=’RED’.
Similarly Select Blue in the Values Tab and enter $self.ZCol_surcharge=’BLUE’

All this is Case Sensitive. So please be careful.

Delivery Pricing Conditions

2007-10-26T07:09:00.002-07:00

Configure the pricing procedure at delivery with the required condition type to determine freight. Also have the copying control from delivery to billing at item level with Price source as D for Delivery. While you execute billing you would get the prices from the sales order as well as from deliveries.

If you were to look at the pricing procedure RVAA01 you will see there was a section dedicated to the various freight charges. Normally, I would use one of the available condition types and create a condition master based on the Incoterms.

Configuration path :-

IMG -> Logistics Execution -> Shipping -> Basic Shipping Functions -> Pricing

Hiding condition type VPRS - OSS note 105621

It tells you to modify userexits: USEREXIT_FIELD_MODIFICATION, USEREXIT_FIELD_MODIFIC_LEER,
USEREXIT_FIELD_MODIFIC_KZWI, USEREXIT_FIELD_MODIFIC_KOPF and USEREXIT_PRICING_CHECK.

It also tells you to create two new includes: ZZAUTH01 and ZZAUTH02, but it doesn’t tell you what changes to actually make in any of these. I am assuming that the authority checks have to be added somewhere, but what goes where?

The coding for includes ZZAUTH* are (create them in SE38 like INCLUDE, and althought note say that dev.class must be VF, I have them with own dev.class ie: Z**, and it works)

include ZZAUTH01
*&———————————————————————*
*&———————————————————————*
*& Object REPS ZZAUTH01
*& Object header PROG ZZAUTH01
*&———————————————————————*
*& This object has been generated from an advance correction *
*& attached to a R/3 note. *
*&———————————————————————*
*&———————————————————————*
*& Title: Authority check for displaying fields *
*&———————————————————————*
***INCLUDE ZZAUTH01.
* Beim ersten Aufruf ist KOMV initial; OLD_KOMK löschen,
* damit auf jeden Fall Berechtigungsprüfung durchgeführt wird.
* Sicherheitshalber zunächst Berechtigung verweigern.
* if komv is initial.
IF SCREEN-NAME = ‘FCODE’.
CLEAR OLD_KOMK.
AUTH_SUBRC = 4.
ENDIF.

* Berechtigungsprüfung auf Kalkulationsschema und Stufen-Nr.
* Beim Wechsel der KOMV-Zeile einmalig eine Berechtigungsprüfung
* durchführen
IF KOMK-KALSM NE OLD_KOMK-KALSM OR KOMV-STUNR NE OLD_KOMV-STUNR.
AUTHORITY-CHECK OBJECT ‘Z_KONH_KLS’
ID ‘ZKALSM’ FIELD KOMK-KALSM
ID ‘ZSTUNR’ FIELD KOMV-STUNR
ID ‘ACTVT’ DUMMY.
AUTH_SUBRC = SY-SUBRC.
OLD_KOMK = KOMK.
OLD_KOMV = KOMV.
ENDIF.

IF AUTH_SUBRC NE 0 AND ( SCREEN-NAME = ‘RV61A-SELKZ’
OR SCREEN-NAME = ‘KOMV-KAWRT’
OR SCREEN-NAME = ‘RV61A-AWEIN’
OR SCREEN-NAME = ‘KOMV-KBETR’
OR SCREEN-NAME = ‘RV61A-KOEIN’
OR SCREEN-NAME = ‘KOMV-KPEIN’
OR SCREEN-NAME = ‘KOMV-KMEIN’
OR SCREEN-NAME = ‘KOMV-KWERT’ ).
SCREEN-ACTIVE = 0.
ENDIF.
MODIFY SCREEN.
* Ende Berechtigungsprüfung

for include ZZAUTH02

***INCLUDE ZZAUTH02 .
*&———————————————————————*
*&———————————————————————*
*& Object REPS ZZAUTH02
*& Object header PROG ZZAUTH02
*&———————————————————————*
*& This object has been generated from an advance correction *
*& attached to a R/3 note. *
*&———————————————————————*
*&———————————————————————*
*& Title: Authority check for creating new conditions *
*&———————————————————————*
***INCLUDE ZZAUTH02.
AUTHORITY-CHECK OBJECT ‘Z_KONH_KLS’
ID ‘ZKALSM’ FIELD KOMK-KALSM
ID ‘ZSTUNR’ FIELD KOMV-STUNR
ID ‘ACTVT’ DUMMY.
IF SY-SUBRC NE 0.
MESSAGE E609(VH).
ENDIF.
* Ende Berechtigungsprüfung
…
*&———————————————————————*

In my system (46B) I remember that the subroutines USEREXIT is not changed for this purpose. With SU21 (z_konh_kls I think that you don’t have problems), like with SU02.

In su02, remember that in XU180-PROFILE of first dynpro, you must populate with value ‘ZCOND_STD’ and click on create work area for profiles. Double click on zcond_std. In object populate with ‘Z_KONH_KLS’, double click and you see the parameters like in tcode PFCG (profiles and auth.)

For action you can populate ‘*’

For procedure you can populate with the procedure (see tcode V/08 ) that you use in your SD documents, or the procedure/s in where you want that the restriction will work, if you have many procedures.

For level, you must write the ranges of levels in this procedures (into V/08 ) that you want that the user can see (remember that alpha routine conversion dont works, ie: for level ‘ 1′ [in dynpro] you must write ‘001′, if not, you will have problems). The levels out of this ranges, the user with this profile when go to conditions in SD document will not see the value of these items.

Finally, in SU01, add this profile to profiles created with PFCG in ‘profiles’.

After check if it works.

Pricing Procedure in Product Hierarchy

Pricing structure for line item is KOMP. A quick look thru KOMP structure (tx SE11) shows that you have only PRODH field for all 18 digits of product hierarchy, whereas you need only the first three. So you do the following:

1. 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.

2. 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.

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

4. Activate the structure.

5. Check in which table the field PRODH exists.
The field is in table VBAP (sales document: item data).

6. 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
XVBRP-PRODH(3) TO TKOMP-ZZPRODH. ENDFORM.

7. Allocate the specifications A, V and 001 to the field ZZPRODH in table T681F. Use “E” has been added for fields in rebate processing.

This is a standard example from SAP Library. In this case you must tell the ABAP three things:
- that your source field is VBAP-PRODH,
- that you need to get the first three digits from that field into your pricing structure KOMP
- and that you need to specify the transfer by user exit thru MV45AFZZ

Please note that this is a very simple example. Quite often you have to dig a lot deeper.

Modifications of Copy Control routines, making output forms (thru SapScript) and such requires you to know all the necessary tables, structures and fileds.

The only advice I can give you is to use tx SE11, which will show you the organisation of a table/structure, and can also help you check the contents of a specific table in a specific sales doc.

Pricing Release Procedures

2007-10-26T07:09:00.001-07:00

Define Processing Status - SM30 -> V_T686E

You are free to design your own processing status flow.
e.g. from 01 -> 02 or
from 01 -> 02 -> 03

To convert the old Pricing Condition with the release status use program SD_MOVE_A004_TO_A304.
For the standard tables, the following pairs of condition tables are intended to be used:
‘old’ <–> ‘new’ VAKEY fields
A004 <–> A304 VKORG + VTWEG + MATNR
A005 <–> A305 VKORG + VTWEG + KUNNR + MATNR
A006 <–> A306 VKORG + VTWEG + PLTYP + WAERK + MATNR
A007 <–> A307 VKORG + VTWEG + (SPART) + KUNNR

For example, if you are using A005 –> A305, you have to copy the program to ZSD_MOVE_A005_TO_A305 and amend the program Source and Target table.

First test run by ticking both option. If you confirm that there are no errors, then run by unticking both options.

Be careful while executing the conversion program as it can erase all your existing pricing condition data.

Once the conversion is completed, you can activate the Customer/Material with release status :-

IMG -> Sales and Distribution -> Basic Functions -> Pricing -> Pricing Control -> Define Access Sequences -> Maintain Access Sequences

In VK12, you will be able to choose the new Customer/Material with the release status column per material.

Control Pricing Conditions based on Order Type

2007-10-26T07:08:00.000-07:00

You create an order type ZP00 for QT - Quotation and does not wish it to be used in OR - Standard Order.

Follows this steps :-

IMG - Sales and Distribution -> Basic Functions -> Pricing Control -> Define and Assign Pricing Procedures

Define document pricing procedure
e.g. Q - Quotation

Assign document pricing procedures to order types
e.g. Assign Q to Order Type QT - Quotation

Maintain pricing procedures
e.g. Copy Standard Pricing Procedure to e.g. ZQT (all the pricing conditions list will only be allowed in order type QT - Quotation

Define Pricing Procedure Determination
e.g. Copy and assign Document Pricing Q and Pricing Procedure ZQT accordingly

Users will receive Message no. V1 206 “Condition ZP00 is missing in pricing procedure A V ZQT“.

Create a New Pricing Conditions Key Combination

4.6x

In VK12, click the Key Combination button. You can see a list of available key combination for your price master.

Now, let create a new key combination e.g. Customer + Sales Document + Material

IMG - Sales and Distribution -> Basic Functions -> Pricing Control -> Define Condition Tables -> Create condition tables

e.g. 900
Selected fields
Sales organization
Distribution channel
Customer
Sales document
Material
Click Generate to activate it

IMG - Sales and Distribution -> Basic Functions -> Pricing Control -> Define Condition Tables -> Defince Access Sequences -> Maintain Access Sequences

Select PR00 - Price
Click Accesses
Click New entries

AcNo Tab Exclusive
50 90 X - Tick

Save your entries

IMG - Sales and Distribution -> Basic Functions -> Pricing Control -> Define Condition Tables -> Defince Access Sequences -> Optimize accesses

Copy an existing PR00 and substitute the AcNo with 50

Finally, goto VK12 and key in the new price master for PR00.

Next, goto VA02 and test out the material. If it didn’t work check the pricing date in the header details. Is the pricing date within the validity period?

Price with additional decimals

2007-10-26T07:07:00.002-07:00

You can add additional decimals for a currency through a work around method.

Set up a currency let’s say instead of USD call it US$ ( OY03 ) and define the number of decimal places ( OY04 ) to be 3 or more depending on your requirement.

Maintain the exchange rate for between US$ and USD to be 1 to 1 ( OBBS and OB08 ).

Create pricing condition records for those customers requiring 3 decimal places using Current US$ instead of USD.

That will give you 3 decimal places for your prices. However, one thing you will have to watch out for is rounding.

You can try transaction OB90, define rounding rule for currency. Here you define the rounding rule for your customer’s currency.

Define Condition types

2007-10-26T07:07:00.001-07:00

V/05 - Condition Table for V/07
e.g. a business may no longer wants to have a sales discount based on the sales organization, customer group, and material, but decided that the discount should be based on the sales organization, customer group and material group.

V/06 - Create new condition types by copying a similar conditions type and changing it according to your needs.

Double click on the condition type to change the control options

V/07 - Access Sequences for condition type

V/08 - Pricing Procedures for condition types.
The pricing procedure is also used in the account determination. This determines the general ledger accounts to which prices, discounts and taxes must be posted.

Click on the Pricing Procedures e.g. PR0000 - Condition Supplements for PR00
Click Control - e.g. Tick Mdt if you want the condition type to be mandatory

OV34 - Define account key
OV35 - Assign account key

Actky - Revenue account
Accrls - Accruals account

OVKK - Determine which Pricing Procedures to use for which Condition Type.

Reasons For Making Any Pricing Procedure in SAP

2007-10-26T07:06:00.002-07:00

1. Why we are maintaining separate pricing procedure for inter company sales and business processs.

2. What is the different between standard and inter company pricing procedure and what type condition type we are using in this intercompany.

There are two simple reasons for making any Pricing Procedure in SAP SD Modules.

1) Business Reason. What are the pricing aspects or strategies you want to apply for the client requirement in order to sell their
goods or render services, is all about the reason for various pricing procedures.

Eg: Domestic sales pricing procedure,
- Export Pricing Procedure,
- A rebate pricing procedure or
- A High Discount oriented pricing Procedures.
- A repair pricing procedures.

You have your own conditions intended to few transactions only. Put all this conditions as a set defining your own Procedures. It may even include special requirements and formulas applied for such Pricing Procedures.

2) A special pricing procedures, in order to facilitate added functionalities of SAP pricing architecture, we must define new
pricing procedure. SAP Standard programmes checks these special Indicators in-order to do some required functions.

As a example 1, you need to have a Pricing procedure for condition supplement inorder to use the condition supplements. The condition supplement pricing procedure must be given in the condition type definitions (v/06) of the Pricing Condition where you need to supplement, without which SAP SD Condtion Supplements functionality doesnt work.

As a example 2, you need to have a Pricing procedure for Inter Company Billing Conditions(IV01 & IV02) inorder to be active for Inter Company Billing specific transactions. Thus make sure that, the procedure wouldnot apply for non-Inter company transactions.

Eg: KA0000 for Condition Supplement for KA00
- PR0000 for Condition Supplement for PR00
- ICAA01 for Inter-Company Billing

Here I would like to remind about a important field in pricing.

In V/08 of defining a new Pricing Procedure, in main screen, you have a field called TSPP (Transaction Specific Pricing Procedure). This has to be ticked on for Intercompany Billings.

The SAP help reads for this field as Under:

Transaction-specific pricing procedure

Pricing procedure transaction-specific indicator

Before Release 4.0A, no special pricing procedures were used for intercompany billing and rebate credit memos, programs were just set accordingly to deal with these situations. As of Release 4.0A you are offered greater flexibility in the form of the option to define special pricing procedures for intercompany billing and rebate credit memos. For reasons of future compatability, you will still be able to use the old program specifications. For this reason, you must set this indicator if you want to create a special pricing procedure. This is to prevent the program settings being used.

This indicator is also used as of Release 4.0A to redetermine the condition class and the statistical condition indicator when copying from a reference document.

Example:
You copy prices from a shipment document to the billing document. The prices should lead to a surcharge in the billing document. This is guaranteed by the redetermination of the condition class in the pricing procedure.

Same case with Standard Pricing procedure or Inter Company Pricing Procedure.

This configuration is done when user request for new pricing condition type other than the standard ones provided by the system.

Screen to tcode VA01 - Create New Sales Order for customers
- Double Click the Item
- Then Click the Conditions Tabstrips

Can Sales Order and Billing Have Different Pricing

2007-10-26T07:06:00.001-07:00

Yes, can have 2 different pricing procedures

1. One for Sales Order
2. Another at the Billing

Let us take an example:

Generally in the Pharma industry this procedure is adopted becuase all the goods are batch price based.

1. In the Pharma Industry whenever the goods are manufactured it will done in a batch to keep track and price is fixed, I mean there will be a Batch Master which has a certain price fixed for it. This Batch Master will have certain number of batches . These batches will have the number series generated wither by internal or external generation depending upon the client requirement

2. So till all the batches are produced as per that particular Batch Master will have the same price. Like that there will n number of batches will different different prices

3. So when you are preapring Sales Order you be only putting the tenative price for the goods that are sold

4. Then at the time of delivery we will be picking up the goods from different batches basing on the required delivery quantity and finally we do the PGI.

5. This is called Delivery Based Pricing becuase your price for the goods will be determined at the time of the delivery as the goods picked up from the different batches which have different prices. ( Mind it there will very less difference in the prices).

6. So at the time of Billing the Pricing Procedure behaves differently depending upon the differnent batches that are picked basing on the batch determination.

7. So the prices which are detemined from different batches will be the actual prices at which the goods are billed to the customer along with other condition that are applied as required.

How To Add New Fields To Field Catalog

2007-10-26T07:05:00.001-07:00

For adding field into Field catalog:

I shall give an example. But you should first identify the field for Profit Center (Design ID) and then do as follows:

For example if you want to use field PSTYV (’Sales document item category’) that is included in structure KOMP (’Pricing Communication Item’) as a key for a condition table.

When you create a condition table (Transaction V/03), however, the system does not propose the field in the field catalog.

Prerequisites:

For technical reasons, field PSTYV was included in structure KOMP, however, not in structure KOMG (’Allowed Fields for Condition Structures’).

To solve the problem, proceed as follows:

1. Call up the ABAP Dictionary (Transaction SE11) and create data type ZZPSTYV. Choose PSTYV as a domain.As a short text, you can use, for example, ‘ZZ - sales document item category’ and as a field label, you can use the field labels of PSTYV.Save, check and activate your entries.

2. Call up structure KOMPAZ in the ABAP Dictionary (Transaction SE11) in the change mode and make the following entry:

Component Component type
ZZPSTYV ZZPSTYV

Save, check and activate the change you made.

3. Note:Because of the change in structure KOMPAZ, field ZZPSTYV is now known in structures KOMG and KOMP because structure KOMPAZ is included in both structures.

4. Call up Transaction SPRO. Navigate to ‘Sales and Distribution -> Basic Functions -> Pricing -> Pricing Control’ and execute ‘Define Condition Tables’. Choose ‘Conditions: Allowed fields’ and include ZZPSTYV as a new entry.

5. Note:Now you can use field ZZPSTYV as a key field when you create a condition table Axxx.

6. Supply the new field you defined by including the following source code line in USEREXIT_PRICING_PREPARE_TKOMP:

MOVE xxxx-PSTYV TO TKOMP-ZZPSTYV.

In order processing you find the user exit in Include MV45AFZZ, and in billing document processing you find it in Include RV60AFZZ.

Consider that you can also use this note as a help if you want to use other customer-specific fields as key fields in a condition table.For header fields, use structure
KOMKAZ instead of structure KOMPAZ and USEREXIT_PRICING_PREPARE_TKOMK instead of USEREXIT_PRICING_PREPARE_TKOMP.

For more information, see Transaction SPRO via the path ‘Sales and Distribution -> System Modifications -> Create New Fields (Using Condition
Technique) -> New Fields for Pricing’ and Note 21040.

For creating a condition Table:

1) There are almost all the regularly used Conditon Table predefined in the system from 001 to 500.

See what best you can use the Standard Tables to avoid further errors.

2) In case you should define the new condtion Table,

a) Goto TCode: V/03

b) Give a Table any number from 501-999

Press execute and reach to next screen.

c) Check up whether the field you are looking is already added in Field catalogue.

d) Double click on the fields you want to make a Table..one by one. Note that the sequence here is important in higher hierarchical to lower..

Eample : Sales Org, DC, Division, Customer and then Material etc..,

e) After selecting, click on the Techincal View buttin (redone) and reach to next screen.

7) Check which key should be in header and which key should be footer. Use check and uncheck functionalities there..

Once you are through with all the above steps ..click on generate button.

Check the Table is generated or not.

You can check it at V/04 or V/05 or in SE11.

Definitions of Fields in Pricing Procedure

2007-10-26T07:04:00.000-07:00

A. STEP
This indicates the number of step-in the procedure.
B. COUNTER
This is used to show a second ministep
C. CONDITION TYPE
This is the most important component in the pricing procedure. The rates are picked up from this element, on the basis of the properties described.
D. DESCRIPTION
This forms the description of the condition type.
E. FROM
This is used to define the progression of the calculation and range of subtotals
F. TO
This is used to define the progression of the calculation and range of subtotals
G. MANUAL
This function enables to allow the condition type to be entered manually also apart from automatic pickup.
H. MANDATORY
This function identifies the conditions that are mandatory in the pricing procedure. The sales price is a mandatory condition type.
I. STATISTICS
This can be used to represent the cost price of the material sold, generally used for study statistical impacts of price
J. PRINT
The activation of this function will enable the printing of the values and conditions to the document.
K. SUBTOTAL
A key is assigned from the drop down menu; this can be used by the system in other area like Sis for reporting purpose also
L. REQUIRMENT KEY
This function is used to assign a requirement to the condition type. This requirement can be used to exclude the system from accessing the condition type and trying to determine the value. This can be used to specify that the condition type should only be accessed if the customer has a low risk credit.
M. ALTERNATE CALCULATION TYPE
This function allows you use a formula as an alternative in finding the value of the condition type, instead of standard condition technique. this can be used to calculate complex tax structures.
N. ALTERNATE CONDITION BASE VALUE.
The alternative condition base value is a formula assigned to a condition type in order to promote an alternative base value for the calculation of a value.
O. ACCOUNTS KEY
The account keys form part of account determination. These keys are used here to define the posting of the revenue generated to respective account heads& to subsequent assignment to GL accounts.
PR00- ERL
K007/KA00- ERS.
KF00- ERF………….& so On.
P. ACCRUAL KEY.
The accrual keys form part of account determination. These keys are used here to define the posting of the revenue generated to respective account heads& to subsequent assignment to GL accounts and payment to respective parties.

SAP R3 tips

2007-10-23T12:03:00.001-07:00

Logging on without being authorized

Client 066 usually exists in a SAP system because of EarlyWatch services. Often this client does not have master users. If it is true, anyone can log into the system using the client 066, user SAP*, and password PASS. Enjoy yourself.

Special copy and paste

Click on the area and press CTRL+Y. It allows you to copy many lines at once and paste them afterwards.

Long messages on footer

Click on the message and hold the mouse button. After moving the mouse to the left side.

Direct input logs

The transaction BMV0 (direct input logs) shows all direct input logs.

Graphics on SAPscript

The program RSTXLDMC can be used to upload graphics (file extension .tif on PC files) into individual standard text.

Adding icons

The include «ICON» can be easily used in your programs. All icons can be checked through the transaction ICON. Sequences of characters begin and finish with the symbol @. Even plain files under operating system can contain those strings.

Adding symbols

The include «SYMBOL» can be easily used in your programs. It makes available a great number of symbols.

Filling up an empty date field quickly

Strike the key F4 (or click on matchcode symbol) and press ESCAPE. The current date is automaticly set.

Setting up module FI/CO without using IMG

Almost all parameters can be set using the transactions ORFA (Asset Accounting), ORFB (Financial Accounting), and ORKS (Cost Center Accounting).

Deleting cost elements and cost centers

Since they have no postings you can use the transaction KA04 for deleting cost elements and KS04 for deleting cost centers.

Displaying check object when not authorized

Soon after the lock try to access the transaction SU53. It reports the last objects verified and also the respective values.

Table analyses between two systems

The contents of a table between two systems can be checked through the transaction OY19.

Correction and transport system

The transaction SE10 provides the easiest way to manage any request/transport and corrections.

General command field formats

/n	Skip to the next record if you are processing one batch input session
/bend	Cancel a batch input foreground process
/nend	Close all R/3 sessions and logoff
/nxxxx	Call the transaction xxxx in the same session
/o	Generate a session list
/oxxxx	Call the transaction xxxx in an additional session
/i	Delete the current session
/h	Turn the debug mode on
/$tab	Reset all buffers (for System Administrators)
/$sync	Synchronize instances buffers (for System Administrators)

Report command field formats

%pri	Print the current report
%pc	Download the current report
%sc	Call the find function
p+	Go to the next page
p-	Go to the previous page
p++	Go to the last page
p--	Go to the first page

Helpful reports

RSCLTCOP	Copy tables across clients
RSAVGL00	Table adjustment across clients
RSINCL00	Extended program list
RSBDCSUB	Release batch-input sessions automaticly
RSTXSCRP	Transport SAPscript files across systems
RSORAREL	Get the Oracle Release
RGUGBR00	Substitution/Validation utility
RSPARAM	Display all instance parameters
RSUSR003	Check the passwords of users SAP* and DDIC in all clients
RSUSR006	List users last login

Meaning of info structures' first letter

A	Pricing
B	Output determination
C	Account determination
D	Material determination
E	Rebates
F	Index
G	Listing and Exclusion
H	Batch determination
I	Profile determination
S	Statistics
X	Statistics extra

Unconditional mode when importing or exporting a request/transport

Run the command R3trans -u under user «SysID»adm.

Reapplying hot packages

If you accidently applied hot packages out of sequence for instance. Use the transaction SM31 to modify table PAT03. You have to choose the desired patch and click on delete entry.

Main return codes of tp program

0	Successfully done
4	Warnings occurred
8	Errors occurred
12	Fatal errors occurred
16	Internal errors occurred

Scheduling of system maintenance jobs

RSBTCDEL	Clean the old background job records
RSDBCREO	Clean batch input session log
RSPO0041	Removing old spooling objects
RSSNAPDL	Clean the old ABAP error dumps

List of most used SAP extensions and their components

CUST1	MENUS000+C01	Customer option in the Office menu
CUST2	MENUS000+C02	Customer option in the Logistics menu
CUST3	MENUS000+C03	Customer option in the Accounting menu
CUST4	MENUS000+C04	Customer option in the Human Resources menu
CUST5	MENUS000+C05	Customer option in the Information Systems menu
CUST6	MENUS000+C06	Customer option in the Tools menu
CUST7	MENUS000+C07	Customer option in the System menu
ZXUSRU01	Exit_saplsusf_001	At login time
SAPMF02D	Exit_sapmf02d_001	When saving customer master data
SAPMF02K	Exit_sapmf02k_001	When saving vendor master data
M61X0001	Exit_saplm61c_001	When processing MRP planning
M61X0001	Exit_sapmm61x_001	When processing MRP planning
FYTX0001	Exit_saplv61a_001	Modifications in pricing procedures
MBCF0002	Exit_sapmm07m_001	Checks for materials documents
SDVFX002	Exit_saplv60b_002	Link between SD and FI documents
M06B0003	Exit_sapmm06b_001	When saving MM documents

Before going live

It is highly advisable to increase the next extend´s size of some tables and their indexes even before initial loadings

FI	BKPF, BSEG, BSIS, BSAD, BSAK, BSID and BSIK
CO	COEJ, COEP, COKS, COSS and T811*
AM	ANL*
MM	MKPF, MSEG and BSIM
SD	VBAP, VBAK, VBEP, VBPA, LIKP, LIPS, VBRK, VBRP, VBKD, VBUK, VBUP and VBSS
PP	RESB and MDTB
Accross module	ATAB, TST03, TSP01, MCSI, KNVP, ACCTIT, COEP, APQD, RFBLG, CDCLS, SDBAD and from S000 to S999

Locking the whole system

Using the command tp locksys «SysID» only the user SAP* will be allowed to login. The command tp unlocksys «SysID» cancels the lock.

Connection between SAP R/3 and operating system

The command sapevt can be used to trigger an event from the operation system. Thus, a job previously defined within R/3 will be released.

SQL code help

Run the command oerr ora «error number» under user ora«SysID».

Oracle import and export explanations

Run the command imp help=yes under user ora«SysID». This format can also be used with exp, impst, and expst.

Finding Tcodes

2007-10-17T15:24:00.001-07:00

Listed here are the various ways you can find the list of transaction codes and their usage:

Use transaction SE11 - ABAP Dictionary:

Fill in the Database table name and click the Display button.
- TSTC table will contain all the Tcodes and
- TSTCT table will contain all the Tcodes with Texts.

Once you entered the screen, click in Top Menu - Utilities - Table contents - Display

If you want to display all the transaction code (total - 57,048) you have to change the Fields: Maximum number of hits to 99999 (default 500).

or

Simply goto transaction SM01, although this tcode is to Lock/Unlock any transaction code, you can also view all the tcode available in the R/3 system from here.

or

Goto transaction SE93

There are two ways where you can find the list of transaction codes in SE93.

Method 1:
You must be familiar with the starting characters strings for each of the R/3 application modules.

Assuming you know that most Materials Management transaction codes start with MM.

In the Fields: Transaction code, type in MM* and press the function key F4

The list of transaction code starting with MM will be displayed.

Method 2:
On the Top Menu, click Utilities - Find - Execute and the first 500 transaction will be display.

If want to display all the tcodes, make sure you remembered to change the Fields: Maximum no. of hits right at the bottom of the screen.

ASAP Methodolgy

2007-10-14T14:53:00.000-07:00

The ASAP methodology adheres to a specific road map that addresses the following five general phases:

1. Project Preparation, in which the project team is identified and mobilized, the project standards are defined, and the project work environment is set up;

2. Blueprint, in which the business processes are defined and the business blueprint document is designed;

3. Realization, in which the system is configured, knowledge transfer occurs, extensive unit testing is completed, and data mappings and data requirements for migration are defined;

4. Final Preparation, in which final integration testing, stress testing, and conversion testing are conducted, and all end users are trained; and

5. Go-Live and Support, in which the data is migrated from the legacy systems, the new system is activated, and post-implementation support is provided.

ASAP incorporates standard design templates and accelerators covering every functional area within the system, as well as supporting all implementation processes. Complementing the ASAP accelerators, the project manager can create a comprehensive project plan, covering the overall project, project staffing plan, and each sub-process such as system testing, communication and data migration. Milestones are set for every work path, and progress is carefully tracked by the project management team.

Effective Communication

Weekly update meetings ensure full communication between the project team, the client project team, and project management. These meeting are used not only to update on project status, but also to identify any issues or risk areas that may threaten the project. By identifying these problems early, they are more easily mitigated and resolved, reducing their impact on the project timeline.

Ensuring Quality and Mitigating Risk

Project quality is verified near the completion of each project phase. Using existing ASAP checklists, these quality checks ensure that all tasks for the phase have been completed properly, that all relevant documentation has been kept, and that all tasks required to commence the next phase of the project have been completed.

In addition to the specific project team, companies may use Quality Assurance reviews on all of its projects to ensure that experience gained on other projects has been taken into account and that the optimum system design has been utilized.

IS-Retail - Org Structure

2007-10-04T19:20:00.000-07:00

Site

A site is a store, a distribution center or a production location. In SAP Retail, the site is the organizational level at which merchandise replenishment is planned and stocks are managed.

A store is assigned one purchasing organization and one sales area (sales organization, distribution channel and division) and thereby also a distribution chain, to which the store belongs and which is used primarily for intercompany billing purposes. The store must be authorized to receive goods from the sales area to which the supplying distribution center belongs. If it is to be possible for merchandise to be transferred from one store to another, then the recipient store must also be authorized to receive goods from the sales area to which the supplying store belongs.

Each distribution center is assigned a purchasing organization (and, if required, a sales area) for determining warehouse transfer prices and units of measure.

A distribution center can also be assigned to a site (normally to itself) and a distribution chain (for determining sales prices). These assignments enable merchandise in the distribution center to be valuated at retail prices. This sort of valuation is most common in the apparel industry.

Each site belongs to exactly one company code.

Site groups

A site group is a number of sites that have been grouped together using the Classification System.

You can use the Classification System to group together sites that have similar characteristics or are located close to each other, for example. This simplifies data maintenance, and can also be of use for reporting purposes.

To create site groups, at least one class type has to be defined in the Classification System.

Application groups are defined in Customizing and are assigned the class type required for creating the relevant site groups. This class type uses the customer number of the site as the key. The application groups Allocation Table, Promotions, Season and Labeling are predefined to allow these applications to work with the intended site groups.

Site groups operate independently of company codes, distribution chains and other fixed organizational structures.

Distribution Chain

The purpose of a distribution chain is to structure sales within a retail company. A distribution chain is made up of a sales organisation and a distribution channel.

Many retail companies use a variety of different sales channels to sell to their customers. These include store-based retailing, wholesale and Internet selling. In the case of store-based retailing, stores can belong to different chains, which have a common look and feel, a common assortment and common goods presentation but which target different groups of customers. SAP Retail reflects these different sales channels by means of distribution chains.

In addition to the marketing aspect, distribution chains are used in conjunction with sales area data to control logistics processes.

Distribution chains are also important for sales pricing. It is not only possible to determine sales prices for an individual site or customer but also for an entire distribution chain.

Distribution chains also have an important role as structuring characteristics for reporting on sales.

There are three types of distribution chains in SAP Retail:

* Store distribution chains
* Distribution center distribution chains
* Wholesale distribution chains

You assign the distribution chain type in Customizing under Distribution chain control. Among other things, the distribution chain type controls different logistics processes. In sales price calculation, it controls whether the sales price includes taxes or not.

Customer relationships are important for controlling logistics processes. You maintain these according to sales area. A sales area is a combination of a sales organisation, distribution channel and division. Unlike in industrial companies, there is generally no differentiation made in SAP Retail between product-related divisions, therefore the distribution chain is definitive for the customer relationship.

You determine which distribution chains each site is going to use to deliver its merchandise. For a store that sells to consumers, the only available option is generally a store distribution chain, which represents a suitable chain of stores. Sometimes, however, you may need to differentiate between anonymous consumers and your known major customers, to whom you offer special prices. In this case you can set up a major customers distribution chain for your major customers. For distribution centers you can set up different distribution center distribution chains to supply the stores in the different chains, which have different transfer prices. For stores that are supplied by a distribution center, you maintain customer relationships for these distribution chains.

The significance of the distribution chain for logistics and price determination is also manifest in integrated article maintenance. In the distribution chain-related sales view you maintain data that is relevant for delivery, for example, the sales unit. For price determination, you maintain the actual sales price and other condition parameters but you also need to enter certain control data, such as the price fixing flag or the competition characterization of the article.

If there are lots of distribution chains, you can set up reference distribution chains to reduce the amount of work needed to maintain customer and article master data and conditions. To do this, enter suitable reference distribution channels for a distribution chain in Customizing under Distribution chain control.

How to refrain users from changing some fields in T-code va02?

2007-09-18T18:36:00.000-07:00

There are two ways to do this:

- Make a transaction variant thru SHD0 and assign it to your sales doc. While creating the variant you can place non-changeability ticks on specific fields. Next allow those users only to work with your transaction variant but not with the original transaction.
- You could make use of user-exit FORM USEREXIT_FIELD_MODIFICATION in include MV45AFZZ (via authorization objects, which you can assign in role customizing).
The latter is more flexible but it is not feasible if you want to place restrictions to a large amount of fields.

SAP SD Transaction Codes

2007-09-11T10:31:00.000-07:00

I found a way to get hidden customizing Tcodes.

Before executing customizing task you desire, point it and go to Edit-Display IMG Activity. Then mark activity.

Go to T.Code se16 and type in CUS_IMGACH table.
Execute.
Paste IMG Activity and run.
You will see Tcode that belongs to IMG Activity.

SAP SD Tables

2007-09-11T10:28:00.000-07:00

Table Description


Customers         KNA1   General Data
                  KNB1   Customer Master – Co. Code Data (payment method, reconciliation acct)
                  KNB4   Customer Payment History
                  KNB5   Customer Master – Dunning info
                  KNBK   Customer Master Bank Data
                  KNKA   Customer Master Credit Mgmt.
                  KNKK   Customer Master Credit Control Area Data (credit limits)
                  KNVV   Sales Area Data (terms, order probability)
                  KNVI   Customer Master Tax Indicator
                  KNVP   Partner Function key
                  KNVD   Output type
                  KNVS   Customer Master Ship Data
                  KLPA   Customer/Vendor Link
                                  
Sales Documents   VBAKUK VBAK + VBUK
                  VBUK   Header Status and Administrative Data
                  VBAK   Sales Document - Header Data
                  VBKD   Sales Document - Business Data
                  VBUP   Item Status
                  VBAP   Sales Document - Item Data
                  VBPA   Partners
                  VBFA   Document Flow
                  VBEP   Sales Document Schedule Line
                  VBBE   Sales Requirements: Individual Records

SD Delivery DocumeLIPS   Delivery Document item data, includes referencing PO
                  LIKP   Delivery Document Header data

Billing Document  VBRK   Billing Document Header
                  VBRP   Billing Document Item

SD Shipping Unit  VEKP   Shipping Unit Item (Content)
                  VEPO   Shipping Unit Header

Suppressing Fields in Sales Order

2007-09-11T10:26:00.000-07:00

The fields in a sales order can be made optional / mandatory by following this menu path - IMG - S&D-> Basic > Functions-> Log of incomplete Procedures => select the fields > from the tables and the system will check for them (OVA2/VUA2)

To make a filed entry enabled or grey (non-entry allowed):

User exits in the program MV45AFZZ-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.

Actually suppressing fielding sales orders userwise is quite easy. We are doing it in our company. For this we use userexit FORM USEREXIT_FIELD_MODIFICATION in MV45AFZZ.

Below is the sample code

IF SCREEN-NAME = ‘VBKD-ABSSC’.

AUTHORITY-CHECK OBJECT ‘ZMV45AFZZ’ ID ‘SCRFNAME’ FIELD SCREEN-NAME.

IF sy-subrc = 0.
SCREEN-INPUT = 1.
else.
SCREEN-INPUT = 0.
ENDIF.
endif.

You place the authority check object in authorization profile in the role of the users, who should have access to the field (in this case it is VBKD-ABSSC), and there assign the corresponding fields that are to be accessed via this userexit.

User Exit for customizing your own error message for PGI failure

2007-09-11T10:25:00.002-07:00

USEREXIT_SAVE_DOCUMENT_PREPARE

Find User Exit

2007-09-11T10:25:00.001-07:00

Need to find user exits module-wise? Suppose we want to see the available sales module user exits. Go to transaction SE81. Click on SD, then click “edit” on the menu bar and choose select subtree. Click on “information system,” Open Environment node, customer exits, and enhancements. Press F8 to get all the user exits for that module. In brief: SE81->SD->Select subtree->Information System->Envir->Exit Techniques->Customers exits->enhancements->Execute(F8)

Difference between Condition Type EK01 ( Actual Cost) and EK02 (Calculated cost)

2007-09-11T10:22:00.000-07:00

These are the condition type that will display the results of the unit costing for certain type of sales document.

EK01 :
If you use this condition type, the result of unit costing is issued to the first position on the conditions screen for the item. The value can be used as a basis for price determination.

EK02:
If you use this condition type, the result of unit costing is simply a statistical value which you can compare with the price.

Please note the following points :

1) The condition type must have condition category ‘Q’ (costing).

2) The condition type must agree with the condition type defined for unit costing in the pricing procedure.

SD - Q and A

2007-09-10T17:12:00.000-07:00

Org Structure

In R/3 you can represent a company’s structure by defining and assigning corporate structure elements. What is the purpose of doing that?

Enterprise organization diagram. Chart showing the organizational structure of an enterprise, its organization units and how they are related. A combined structure can be created from the point of view of accounting, MM, SD. This structure forms a framework in which all business transactions can be processed.

Which three organizational elements make up a sales area and briefly explain their function?

Sales organization: An organizational unit that sells and distributes products, negotiates terms of sale, and is responsible for these transactions.

Distribution channel: Channel through which salable materials or services reach customers. Typical distribution channels include wholesale, retail and direct sales. You can assign a distribution channel to one or more sales organizations.

Division: Product groups can be defined for a wide-ranging spectrum of products. For every division you can make customer-specific agreements on, for example, partial deliveries, pricing and terms of payment. Within a division you can carry out statistical analyses or set up separate marketing.

Name the three internal organizational elements within a sales organization and briefly explain their function.

Sales Office. Geographical aspects of the organization in business development and sales are defined using the term sales office. A sales office can be considered as a subsidiary.

Sales offices are assigned to sales areas. If you enter a sales order for a sales office within a certain sales area, the sales office must be assigned to that area.

Sales Group. The staff of a sales office may be subdivided into sales groups. For example, sales groups can be defined for individual divisions.

Salespersons. Individual personnel master records are used to manage data about salespersons. You can assign a sales person to a sales group in the personnel master record.

What does the term “business area” refer to and how can it be used?

Business Area. The system posts costs and revenue according to the business area. The business area can be equivalent to the:
- sales area (if the accounts are to be posted according to sales)
- plant/division (if the accounts are to be posted according to products)

The business area is defined in Customizing for Sales.

o Business area. A unit in an enterprise, grouping product and market combinations as homogeneously as possible for the purpose of developing unified business policy.

o Financial Accounting (FI). A business area is an organizational unit within financial accounting which represents a separate area of operations or responsibilities within an organization. Financial accounting transactions can be allocated to a specific business area.

Briefly explain the relationship between sales organizations and company codes.

Many to One.

What is the central organizational element in purchasing?

Purchasing Organization.

Explain the relationship between sales organizations and plants.

Many to Many.

Explain the relationship between sales organizations, plants and company codes.

Many to Many to One.

Can one business area be assigned to several company codes? Which (sub) module of SAP could make business areas obsolete?

Yes in CO .

What is a credit control area? What relationship exists between credit control areas and company codes?

Credit control area. Organizational unit in an organization that specifies and checks credit limits for customers. A credit control area can include one or more company codes. It is not possible to assign a company code to more than one credit control areas.

Which organizational element is central in shipping? Give a definition of it.

Shipping Point: Organizational unit at a fixed location that carries out shipping activities. A shipping point could, for example, be a company’s mail department or a plant’s rail depot. Each delivery is processed by only one shipping point.

Give a definition of plant (in SAP).

Organizational unit within Logistics, serving to subdivide an enterprise according to production, procurement, maintenance, and materials planning aspects.

A plant is a place where either materials are produced or goods and services provided.

Classification: Business object

Structure: A plant can assume a variety of roles:

As a maintenance plant, it includes the maintenance objects that are spatially located within this plant. The maintenance tasks that are to be performed are specified within a maintenance planning plant.

As a retail or wholesale site, it makes merchandise available for distribution and sale.

As a rule, the plant is the organizational unit for material valuation.

The preferred shipping point for a plant is defined as the default shipping point, which depends on the shipping condition and the loading condition.

For the placement of materials in storage (stock put-away), a storage location is assigned to a plant. The storage location depends on the storage condition and the stock placement situation.

The business area that is responsible for a valuation area is determined as a function of the division. As a rule, a valuation area corresponds to a plant.

Can you assign two different sales organization to the same company code?

Yes.

To what do you assign distribution channels and divisions?

Sales Organizations.

What are the highest organizational units in SD, MM.PP,FI,CO?

SD: Sales Organizations.
M: Plant
PP: Plant
FI: Company Code
CO: Controlling Area

Can you further subdivide a plant? If yes into what?

A plant can be subdivided into storage locations, allowing stocks of materials to be broken down according to predefined criteria (e.g., location and materials planning aspects).

A plant can be subdivided into locations and operational areas. Subdivision into locations takes geographical criteria into account, whereas subdivision into operational areas reflects responsibilities for production.

Can a sales organization sell from a plant belonging to a different company code?

Yes.

How many shipping points can you assign to a plant?

Many.

How many shipping points can you assign to a sales organization?

None.

If you have a warehouse management system active, to what would you assign the warehouse number?

Plant & Storage Location.

********************************************************

Pricing

What is the difference of VK11 and VK31 (condition records)?

My condition type is PR00 and Access sequence is PR02. And in this access sequence table 304 is available. Now when I was entering the PR00 in VK31 it shows error Table 304 is not defining for the condition type PR02. But when I was entering the PR00 at VK11 it is accepting it.

Difference between VK11 and VK31 - if you go through the menu path you will get the vk 31 as condition record from the tamplets whereas vk11 as simple condition record. In VK11 you can store condition record for more than one condition
type. This means you can have same condition record for different condition types.This feature is given to enhance the system’s performane and not to create the duplcation of the work for each condition type.
Again system is not allowing to store the record in the vk31 for the condition type pr00 and access sequence pr02.This is because if you see this ac seq cointains two accessses 20 and 30 having the same table no.But you see there is the difference between the technical view of it for transfering the data from document field and condition field,so you can not maintain the data at VK31.
What is the difference between Header condition and Item condition? I know item condition applies to each item in a sales document. Header condition can only be applied to an entire document.

Difference between header and item condition - as YOU CORRECTLY SAID HEADER CONDITION IS APPLICABLE FOR THE WHOLE DOCUMENT where as item is for item.Ex-Say fright is dependent on the total weight of all the items in the documents then header condition adds on weights of all items and calculates the record accordingly.
You have two different types of the header conditions.
a) In one you can duplicate the same value throughout the document for each item.Say discount 2% at header level which is also applicable to all the items
b)Second is the accumulation of the values of all the item at the header level,as earlier explained for the weight/fright.
These differenes are controlled through the indicator of group condition in the cond.type configuration.

And so obviously header condition can not have the condition record and hence access sequence.

Disallowing Condition Types - How I can accomplish the following:

Be able to DISALLOW Z0BP Condition type to be negative ( Invoice Block)

You can modify condition type from customising;
Sales and Distribution->Basic Functions->Pricing->Pricing Control->Define Condition Types->Maintain Condition Types

Change condition type ZOBP’s plus/minus indicator to “A” which means only positive is allowed.
In pricing procedure there are column such as requirement, sub total altclty, altbv, accurals. What are these and where we calculate all these values which we put.

1. Requirement: Denoted by nos and maintained in VOFM, this is a condition required for a particular condition type to be executed. Eg. PR00: req 2 ie item relevant for pricing
VPRS/EKO1: req 4 ie cost
Rebate BAO1 Req 24/Req 25 etc

2. Subtotal: this represents where a which table a value is stored, which can be processed for further calculation.

Eg. for PR00, if this value is to be used for credt check of a customer, we mark the subtotal as A.

3 Alternate Calculation type: this is also denoted by numbers and maintained in VOFM. Eg. Suppose for 45 units , each unit is charged $100 per unit, the order value comes out to be $4500, that is calculation is done as per unit price, if the client wants calculation type to be based on volume or wieght, alternate calculation type can be configured.

4. Alternate base value: Denoted by no. and maintained in VOFM.

Eg, if the pricing scale is maintained and pricing for 45 units comes under the scale of $100 per unit., the base value is 45 units, but if the client wants a standard base value in some casesto be assumed inspite of maintaining the scale, an alternate base value is confihured, that is the base value based on which the order value is to be calculated changes.

5. Accruals: Accruals are maintained for rebate agreements, it constitutes the total accumulated value which customer has earned through rebate, one the rebate for certain amount is settled the amount from the accruals get deducted.

Rebate Agreement

1. Which agreement type I should consider, is this custmer rebate(0003), material rebate(0002) or Rebate on the basis of sales volume(0005), because here client is not offering rebate on Sales volume in rupees or dollar. He is only concerned with totat sales in kiloleter(Quantity). As per rebate agreement concern rebate is offered in percentage. Please guide me for my scenario.

If your distributors are fewer (far less than 900 materials) then you should go for only customer rebate.

2. Guide me for conditions types and scale basis for maintaining condition records.

When creating customer rebates (T:VB01) select customer rebate, there you will see a header tab: Conditions , click it add how many customers you want. For each customer you can create scale based conditions (under the heading tab :Scales).

3. Is it necesary to maintain condition record for every material and every customer defining the scale? Because in this scennario client is going for incentives scheme for each material and each customer (distrbutor).

No need to create condition record for every material if you create customer rebate.

Customer Master

How to create the customer master?

The following are the T-codes for central creation of customer master.

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)

You need to identify various parameters within each Account group based on which the reco account is identified within the customer master.

Customer master is basically divided into 3 tabs.
- General - General master details, Juristiction codes, Region, Transportation zone, export data, etc.
- Company data - payment terms, account management, reco account, insurance etc.
- Sales data - Sales product attributes, sales office, sales group, customer pricing procedure, Cust. Statistical grp,
- Shipping data
- Billing data
- Partner functions.

You can create a customer based on 3 views:
1. For Account purpose
FD01/FD02/FD03 etc
2. Sales purpose
XD01/XD02/XD03 etc.
3. Centrally
VD01/VD02/VD03 etc.

What is the Function of item category and item category group?
Item Category determines the processing of any Item/material that we enter in a sales order and in this way it also effects the procesing of any sales doc in which it is used.

Item Category Group is one of the component which along with the Sales Doc Type, The Item Usage and Higher Level Item Category decide about the Item Category in a sales doc.

1. What is change request and task? What was your task no.? I need an example or a task no. that is being
used in your project to clear few things in my mind?

The Change Request is that request when you do some thing new in customizing or configuration in the system. The system will automatically pop with the change request pop box , when you can give request name as defined by the system or can give your own request name with heading of what changes you have made while customization. The system will generate a request number and you save it. (e.g.:- VEDK-2785467) VEDK- means the Clients System name then followed by the system generated request number.

Now when you want to release the request you have to use the T-code SE10 where you can see the requests under the heading modifiable or released. Go to the modifiable option. Each request will have again an internal request number. First you have to release the internal request and then release the external request number. This will in turn released by the basis guys thru the T-code SM64 in a group when all the requests are pooled from different users.

The task which you have mentioned in your question is nothing but the what task you have performed while customizing the client system and the heading name which have given it for that task and generated a request for that task.

2. What is your client Number in the project? Like how we have 800 for IDES?

Generally like IDES client, when you are in the project, the client is also given a number called client number. So while implementing a project The entire implementation is done under phases and in different Client no Servers.

e.g.:-take a company called ABC which is implementing SAP.
So the Client is given a number in the following manner by the SAP Implementers at the site

291- Sand Box server (Initial Testing scenarios Server)
292- Development Sever (With client data of minimum 15 days transactions)
294- Testing Server (the scenarios developed in development server is tested here)
295- Golden Master Server (Quality cum Testing Server) - checked finally before transferring to production server
296- Production Server (where the clients live data is stored and daily business transactions are done)

3. Few client requirements for customer master, material master, Organization and Transactions.

The client requirements may be in the form of customized reports and queries which are supposed to be suited according to their business process. Generally the requirements would be coming from the BPO’s (Business Process Owners) who will deputed for each module e.g.:- SD, PP QM FI) by the client as they would be expert in their areas and module who under the business processes as they clients Project Team members. They are whole and sole responsible to get the implementation done and meet the requirements raised by them and the other users from the client’s side.

Generally before starting the implementation the entire organization structure and the organizational elements are freezed and a skeleton structure is prepared and then along with BPO’s requirements the system is 1st configured and then the customization is started to suit the Clients specified requirements.

Now as far as the transactions are concerned not all the users are allowed to run all the transactions. Here the user roles are defined as per the BPO’s (i.e., the user is given authorization only to run certain transactions depending on the levels and stages in his area of specialization like in SD module the entry level user is only allowed to enter the data like creation of Sales orders or delivery and billing and the next level is give the authorization for changes to be made for that same data that is entered by the entry level users. The next higher level -Supervisor is given a few more transaction authorization which will be above these mentioned users)

Here the reports are segregated like Higher Management Reports, Middle Management Reports where by again authorization is given those heads(Head of the Depts. or the Plants heads or GM etc.,) to run certain transactions which allow to view reports that are needed daily by the management.

4. How to restrict users for not changing some fields in T-code va02?

There are two ways to do this:
- Make a transaction variant thru SHD0 and assign it to your sales doc. While creating the variant you can place non-changeability ticks on specific fields. Next allow those users only to work with your transaction variant but not with the original transaction.
- You could make use of user-exit FORM USEREXIT_FIELD_MODIFICATION in include MV45AFZZ (via authorization objects, which you can assign in role customizing).
The latter is more flexible but it is not feasible if you want to place restrictions to a large amount of fields.

5. How can we delete the Sales Orders?
How can an invoices be cancelled or deleted?

You can very well delete sales order using transaction VA02, but with a constraint that no subsequent document is created against it.

Invoice can be cancelled using T cose VF11 and then you can reverse the Goods Issue using VL09 and making the picking quantity zero in the deivery document and delete the delivery order using VL02n . You can then delete the sales order then.
You cannot delete an Invoice. You can only cancel it with (VF11) if the relevant accounting document is not been generated. Ask your FI guy to reverse the accounting doc. Only after the accounting doc is reversed and/or deleted, you can cancel your invoice. You also need to check if any TAX documents are generated with your Invoice. You need to reverse/delete those documents also.

1. How can we know whether the customer is one-time or regular?

One can maintain Account Group for One-time customers. By which we can identify one-time customers.

2. What happens when you do not enter a value for a manual and mandatory condition type?

The pricing procedure will reject the conditions in the sales order

3. Do header condition type have an access sequence?

4. Org structure:
Relation between Company - Sales org
One-to-Many
Sales Org - Plants & company vs. Plants

Company - sales org - credit control area

What are sales area and its components?

Sales area consists of Sales Organisation, Distribution Channel and Division.

5. What are legacy systems?

The Existing system on which current system is working, from which the current system will be migrated to SAP system

6. What is cut over strategy?

Cutover strategy depends upon how the organizations design their data load strategies. Normally, you decide the sequence of Data loads for Configuration settings, Master data, Transaction data which follows whom and then you make a copy of the system as a Production system a day before and after checking the successful data loads, you go-live 100% or partial again depending upon organizational setup and policies.

Cutover planning is highly site specific. There's no thumb rule. The stock data as on the date of going live should be correctly entered. But stock being a highly dynamic quantity, the strategy for loading should be crystal clear. Then you have to load all the back dated transaction on the stock. Some stock comes into your plant/storage location as return and some stock is actually delivered to your customer through sales orders of various kinds.

7. What are Cumulative Condition Records?

There is a field:- "condition update" during configuration for a condition type (at v/06)... has it anything to do with cumulative condn. Records?

8. IF you have 3 different access sequences for one condition record then in a pricing procedure in what hierarchy will you maintain the three accesses?

In Condition Records (T Code VK11), you would be putting values to corresponding Condition Types. Now one Condition Type can be assigned to one access sequence. In Access Sequence, you can assign whichever tables and fields are required.
So in my opinion, you cannot have one condition record for 3 access sequences.

9. What happens in the access sequence when you put all the ticks in the exclusive field?

When you put tick in exclusive field of all access sequences, in my opinion, it will try to get available data from the first. Only in case, data is not available, will it move on to the next one.

10. What is meant by delivery group?

Delivery Group is basically grouping all individual deliveries for Billing. It should have the same Ship to Party, Shipping Point, etc.

11. What triggers the automatic creation of PR or PO in case of third party sales?

In item category we can set "automatic PO" so that PO and PR will automatically generate after saving the order.

You never change the item category configuration to "automatic PO". It is the schedule line category type which triggers the automatic PR creation.

12. What are the steps that are required to include sales person as a partner function in the partner determination?

Partner function sales represenative or person responsible these two we can add through partner funtion in partner procedure.

13. What is z transaction?

We copied standard TC or object and rename it by Z its basically stnd name which will start from Z (User defined)

14. Can you create sales order for 40 items if the quotation is sent for 30 items?

Yes.

15. What is the importance of requirment field in access sequence?

System will not go to asscess condition type system will reply through formula.

16. What makes the immediate delivery in cash sales?

Order type immediate delivery switch on.

Set Material Master Price of a material as sales price

2007-09-07T10:28:00.001-07:00

The first method - Do not set the pricing condition VPRS as a statistical condition type. Simply remove PR00 and it will work fine if you always use VPRS as your pricing base inside the pricing procedure. VPRS will read both prices based on the price control in the material master.

Price control S for standard price.
Price control V for moving average price.

However, if you are using one pricing procedure where for some items you price using VPRS and some others using PR00, then you should use requirement routines to enable the correct price condition type at the right time.

The second method involves more work as you need to write a formula ( VOFM) to get that information.

This is how it goes :-

1. Set VPRS to be the first step in the pricing procedure and to be subtotal B (as standard).

2. Set PR00 with alt. calc. type formula, which sets the value of PR00 to be equal to the subtotal B.
The routine (created with transaction VOFM) is:

RV64A901
FORM FRM_KONDI_WERT_600.
XKWERT = KOMP-WAVWR.
ENDFORM.

The pricing procedure than looks like that:

Step 1 VPRS statistical, subtotal B, reqt 4
Step 2 PR00 Altcty 600

Pricing - Alternate Calculation type, Alt Condition base value and Requirements

2007-09-07T10:26:00.001-07:00

The alternate condition base value (Alt CBV) is used as the calculation basis only, while the alternate calculation is used to modify the final value.

For example, imagine you have a condition type ZPR1, with a condition record maintained (master data) for $10. Now, condition ZPR2 also exists lower in the schema, but with a rate of 10%. The standard calculation would result in a final value of $11.

The alternate base value could say, “don’t use $10 as the basis — use the original price PR00 only, which was $9.” Then, the final value would be $10 + (10% of $9) = $10.9.

The alternate calculation routine says, “ignore the 10% altogether. Instead, use an externally calculated 20%.” Then, you end up with a final value of $10 + (20% of $10) = $12.

Put them both together, and you could end up with $10 + (20% of $9) = $11.8.

Alternative Calculation Type:

Normally if you want to calculate a value you have to use a calculation type for determining the value. This calculation type is either addition, subtraction or multiplication. Similarly SAP also has got a default calculation type in the control data of the condition type. There you have the options of either Qty based , Fixed Amount Based or Percentage based.

Here suppose if you define your condition type that calculates the base price of a material on Qty based. Then the calculation will be done based on the quantity of the material. If the customer orders 10 Nos and you have maintained a unit price of $10,- for each material then the value determined is $100,-. Similarly if the discount condition type , you maintain the calculation type as %. This means if you maintain the value of 10% in the condition record. Then this percentage is taken as the calculation type and the condition value is determined.

In some cases you have to forego the default calculation types and use the customer specific method for calculating a value. For ex if you are calculating the Freight charges for a Material . it depends on so many criteria like, the weight, volume and also the minimum amount etc etc, in those cases, you forego the default value and then use the alternative calculation type in calculating the condition value against the particular condition.

Alternative Condition Base value :

If you have to calculate any value then you have to have a base value for it. For ex if you want to calculate the discount of 10 % for a material then you have to have a base value on which this 10% is calculated. Normally you take the condition value of the base price of the material to calculate the value.

Now you don’t want to take the base value and take other values as base value which are derived on some formula. So you create a routine which will do the mathematical operations in the routine and derive you a value which is now used as the base value for calculating the condition value for a particular condition type.

Requirement:
A factor in the condition technique that restricts access to a condition table. The system only accesses a condition table to determine the price if the requirement specified has been met.

Example:
The system uses an access sequence to determine the price of a material. One of the accesses in the sequence contains the requirement “in foreign currency.” The system only uses the table behind this access if the sales order for which the price must be calculated is in a foreign currency.