SAP SD FREE MATERIAL

PLEASE BEAR WITH ME ! YOU MAY NOT SEE POSTS I CREATED AFTER 2017

2021-10-02T23:25:00.006+05:30

DEAR ALL,

I UNDERSTAND THAT YOU ARE HERE READING THIS BLOG TO FIND OUT SOME NEW CONTENT RELATED TO S/4 HANA SALES AND TOPICS LIKE FSCM CREDIT MANAGEMENT, AATP, CONDITION CONTRACTS ETC.

UNFORTUNATELY THE DOCUMENTS I CREATED ARE NO MORE ACCESSIBLE DUE TO SERVICE CHANGE OF A DOCUMENT REPOSITORY WEBSITE WHERE I USED TO SAVE THE DOCUMENTS.

SEVERAL POSTS HAVE BEEN IMPACTED. MOSTLY THE POSTS FROM 2014 TO 2017 AND THEN ALL POSTS FROM 2018-2021.

I HOPE TO SHARE SOME REALLY EASY TO UNDERSTAND PRACTICAL DOCUMENTS WITH YOU. BUT IT MAY TAKE A LOT OF TIME AS MY WORK SCHEDULE HAS BEEN VERY BUSY THESE DAYS.

MEANWHILE PLEASE GO THROUGH THE SAP PRESS BOOKS AND CERTIFICATION BOOKS. NOTHING CAN BEAT THOSE WHEN IT'S ABOUT GETTING YOUR CERTIFICATION CLEAR AND GETTING CONCEPTS UNDERSTOOD.

WISHING YOU ALL THE VERY BEST. AT LAST, THANK YOU FOR BEING HERE !

THANKS

MANOJ

Quick Bites - Partner Determination in Nutshell

2017-11-11T20:38:00.000+05:30

Partner Determination in Nutshell

Partner Determination is used at various levels all over the SAP. From SD Point of view, Partner determination is used at the following levels:

Customer Master Partner Determination
Sales Document Header Level
Sale Document Item Level
Delivery Document
Shipping Document
Billing Document Header Level
Billing Document Item Level
Sales Activities (CAS)

Below is the high-level Overview of how Partner Determination works in SAP:

OUTPUT DETERMINATION in SAP - Billing

2013-04-15T14:55:00.000+05:30

PARTNER DETERMINATION IN SAP

2012-09-22T07:32:00.000+05:30

SAP Partner Determination for Customer Master

CREDIT MANAGEMENT

2012-01-31T20:41:00.000+05:30

Credit Management -

TAX determination in SD

2011-08-08T13:22:00.000+05:30

Define Tax Determination Rules

You specify the valid tax types in transaction OVK1. More than one tax type can be defined for a country by defining the sequence.

The SAP System determines the taxes automatically within pricing.

In the standard SAP R/3 System, the elements of tax calculation are predefined (for example, tax condition type "MWST" for taxes on sales and purchases).

Assign the plant for Tax Determination in OX10, using the country key, the SAP System recognizes which tax type is valid for a plant and thus which taxes are relevant when creating an SD document.

Define the Customer Taxes in OVK3, you will maintain the tax code in Customer Master.

Define the Material Taxes in OVK4, which will then be maintain in Material Master.

For example :-
MWST GST 0 Tax Exempt
MWST GST 1 Liable for Taxes

Now, you define the Tax Determination in VK12.

VK12 - Domestic Taxes/Export Taxes

Condition Type MWST

Customer Taxes Material Taxes Rate Taxes
0 0 0 %
0 1 0 %
1 0 0 %
1 1 9 %

In this example, if both the Customer Master and Material Master Tax code is 1, Tax will be included when you create the Sales Order.

Tax Code in Customer Master / Sales Order

How can we maintain the Tax Code (Tax code - which we maintain in MWST Condtion Records) in Customer Master or in Sales Order?

There are few points which I would like to remind you:

1) MWST is a tax condition which is applied to customer to whom we are selling. The rate of tax is depend on various parameteres, whether is fully liable for tax or expemted (in case of Defence Customer)

2) There are few parameteres which we apply tax condition. Whether customer is tax liable? Whether material is tax exempted?

For example, if you are selling a goods which are free for tax to any customer, put the Tax Indicator (at MMR as '0'). If your
material is tax liable pur the Tax Indicator (at MMR as 1). If your customer is not liable for tax at all (like the case of Indian
Defence organisations) put the Tax Indicator (at CMR as 0) or 1 in case fully tax liable.

3) Now, at VK11 you need to mainatain your pricning conditions with all the combinations like:

1 0
1 1
0 1
0 0

4) While maintaining your Material Master Records or Cusotmer Master Records, you must identify, which are tax liable and which are tax exempeted.

5) In anycase, as a SAP standard Best Practises, while processing a sales order, you must retrieve a Tax condition record from SAP database only and not entered Manually. Accordingly, at V/06, the MWST condition Defintions, the field for 'Manual Entries', it would be marked as - D (Not possible to process Manually).

Due to this setting, normally, you cannot maintain Condition tax code during sales order processing. And in Cusotmer Master, you can only maintain Tax Indicator and not Tax Code.

6) In case your client insists for Manual entry of Tax code during Sales Order processing, you can change the field at point 5) above to C-Manual entry is priority instead of D.

=======================================================================

Taxation Explain with an example
I'm assuming that, the country is India and based on its requirement:

Sales tax is a state government revenue. There are two types of sales taxes, Local sales tax & central sales tax. Local sales tax is intra state whereas CST is inter state.

Example of LST : Point of sale i.e. delivering plant & ship to party are within the same state. The rates are defined by the respective state governments.

Example of CST : The Delivering plant & Ship to party geographic locations are 2 different states. At the point of sales from one state, the ST goes to that state govt. & consignment is despatched to the Ship to party. Once that consignment is received at the ship to party state, sales tax will be levied once the sales is registered there. For this case, the LST that is applicable by the Ship to party further will not be applicable in all probability to be captured in SAP.

Stock transfer : This does not attract any sales tax. The consignment is transferred from one D plant to another D plant irrespective of inter/intra state sales. The invoice that is accompanied with the consignment thus shall not have any final value. It's a zero value invoice, but the basic prices needed to be mentioned.

The selling organisations normally needs to register with the sales tax authority of the respective state to have a warehouse or D plant to avoid the double taxation for their dealers/distributors.

Now, the pricing procedure that is there in 4.7 is Factory sale with formula-JFACT, in which the CST condition type is JIN1 & the LST is probably JIN2. There may be surcharge cond types as well which will calculate the amount on either JIN1 or JIN2.

For config :

1.SPRO > S&D > Basic fn. > Pricing > Pricing control > Define & assign Pric. procedure > Maintain Pric proc.

2. The tax rates are normally driven from the Tax classification of Customer & Material access. To do this config, S&D >Basic fn. > Taxes. You need to include the condition type for country IN in 'Define tax determin rule'.

3. Same path : But go to Tax relevancy of master records where you configure the condition type & options of rates that will flow to these masters. One needs to understand here properly as u need to have unique combinations for picking the sales tax rates. I will try to demonstrate the smallest example. Let's say, the LST rates are 2%,4% & 0%. I will have two options for material master here. 1 for taxable & 2 for not taxable.

For customer master, I will have 1-LST 2%, 2-LST4% & 3-LST0%. When I create master records for LST thru VK11 for JIN2, I will chose the access where the combinations of customer & material tax classifications are available. If this access does not exist create it under an access sequence. But normally this is standard. The condition records will look like,
Cust-Tax classi. Material tax claasi. Rate Tax code
1 1 2% A1
2 1 4% A1
3 1 0% A1

Remember, rates are flown from the tax codes. Tax codes can be created thru T code FTXP. This is normally a FI job.

How to create t-code from SQVI query?

2011-07-27T11:33:00.002+05:30

How to create t-code from SQVI query?

If you have created a query report from sqvi t-code, you can generate a new t-code for that report, so you can share it to other users (since sqvi query cannot be accessed by other users). You can do it as follow steps:

Select your query on the SQVI screen and accessing the menu: "QuickView - Additional functions - Generate program"
Display the program name by accessing menu: "QuickView - Additional functions - Display report name". Copy that program name.
Open t-code: SE93. Input your new t-code name (begin with "Z" letter) in the "transaction code" field.
Click "Create" button.
Input the new t-code description and choose "program and selection screen (report transaction). Press "enter".
Paste the program name of your sqvi query into the "program" field.
Click "save" to create your new t-code that execute your sqvi query.
You can give the authorization for the new t-code to any users.

Variant Configuration

2011-07-25T11:53:00.006+05:30

Steps for SD Variant Configuration (Basic Steps)

1.) Create a Material - KMAT type with Item category Group(002)

2.)Create Charateristics in CT04 - Zbike, where in values mention the Color of the bile like Red, Blue etc

3.) Create another characteristics in CT04 - ZPrice, where directly go the additional data tab and maintain the table SDCOM and field VKOND (ABAP Dictionary it will ask for)

4.) Assign these two characteristics to a Class in CL01 - ZBikeclass ( Type 300) in characteristics tab page.

5.) Then go to CU41 Configuration profile select the material and enter the description click on the class assignment ie assign Zbikclass.

6.) Now go back to CT04 - enter Zbike -go to values- select Red- go to extras - Other Dependencies -

Select Procedure enter in front 10 write - $self.ZPrice='Red' and save

Now go back go to extras - Other Dependencies - assignments and assign relationship ( by default it will come just save)

Now select Blue- go to extras - Other Dependencies - Editor - Select Procedure enter in front of 10 write - $self.ZPrice='Blue' and save

Now go back go to extras - Other Dependencies - assignments and assign relationship ( by default it will come just save)

7.) Now go to VK11 - Enter VA00 (Condition)(For Std RVA001 Pricing Procedure) - enter variant Red and Blue give the rates accordingly and create the sales order.

EMBEDDED DOCUMENT 001

Variant Configuration

EMBEDDED DOCUMENT 002

variant-configuration-kt

<< A PRESENTATION ON THE VARIANT CONFIGURATION IS GIVEN BELOW >>

A Presentation By Arun Prasad (Courtesy of Slideshare )

Variant Configuration Overview

Useful for SD and MM Guyz For Knowledge Point Of View

Regards,
Manoj

SAP SD INTERVIEW QUESTIONS

2011-07-25T11:24:00.000+05:30

A Collection From Internet Resource :

What is transfer order?
What are the fields in pricing procedure?
What are the Standard output types in SD?
What is Condition type?
What is difference between delivery document & scheduling?
How is item category determined?
What is Extract used in condition tech. in pricing?
What is the difference between plant and storage location?
What is the difference between item proposal
What are the statuses?
What is Lean Warehouse Management?
What is the purpose of sales document type?
What is an integration point between SD AND MM?
What are MRP types?
What is use of customer group?
What is the difference between incomplete order and backorder processing?
Why does the customer master have different views?
What is t-code for listing the blocked documents?
What is batch split?
What is Product attributes?
What is difference between SD account key and FI account key?What is a variant and its use?
How is credit control determined?
What are the parameters in FD32?
What is the difference between routine and requirements?
What is condition supplement and why is it used?
What is the difference between milestone and periodic billing?
What is the landscape?
How variant is used in reporting?
What is the difference between Static and Dynamic Credit Check?
What is difference between the item proposal and dynamic proposal?
What are the issues u have faced in integration testing?
What is a field catalog?
What is the difference between condition type EK01 and EK02?
What are the user exits?
What is the Function of item category group?
What is pricing procedure?
What is condition exclusion?
Which delivery document type for STO process?
What is difference between the header level condition
What is the link between credit management and subtotals?
What is Delivery group and what is its purpose?
What is main purpose of maintaining the master data?
What is line item?
What is a Transfer order?
What is value SAP?
What is difference between listing and exclusion?
What happens when you overrate the customer?
What are the functions performed in a support client?
What is the access sequence for header conditions?
What are the highest organizational units in SD, MM, PP and FICO?
What is the functionality of negative posting in billing document?
What is mean of Rebate processing?
How is shipping point determined?
What is difference between transport and task?
What is the client specific data?
What is ABAP debugging?
How subtotal in pp is related to credit limit?
What is the difference between discount and rebate?
What are the routines?
What are the reports u have generated with help of ABAP?
What are all the things we need to do configure
What is meant by Variant Configuration?
What is the relation ship between sales organization
What are the influencing factors for account determination
What are the influencing factors for account determination
What are dependencies in variant configuration?
How alternate condition base value?
How alternate condition base value?
What is the use of pod?
What is difference between listing and exclusion?
How revenue account is determined?
When will you combine deliveries into one invoice?
How will be the Ticket process flow happens in a Production support project?
What is transfer order?
What are the fields in pricing procedure?
What are the Standard output types in SD?
What is Condition type?
What are the issues u have faced in training?
What is difference between delivery document & scheduling?
How is item category determined?
What is Extract used in condition tech. in pricing?
What is the difference between plant and storage location?
What is the difference between item proposal
What are the statuses?
What is Lean Warehouse Management?
What is the purpose of sales document type?
What is an integration point between SD AND MM?
What are MRP types?
What is use of customer group?
What is the difference between incomplete order and backorder processing?
Why does the customer master have different views?
What is t-code for listing the blocked documents?
What is batch split?
What is Product attributes?
What is difference between SD account key and FI account key?
What will you do in blue print stage?
How will access the data in to production?
What is transfer order?
What is Group condition?
What is cut over strategy?
What is the relation between PGI and TOR?
How is route determined?
What is consumption based planning?
What is the relation ship between sales organization and plants?
What is Item Category Control?
What is Returnable packaging processing means?
What is IMG?
What are the Differences between invoice and billing doc?
What is the relation between sales organization and company codes?
What is Replenishment lead time?
How can we create user exits?
How can we create user exits?
Where is shipping conditions stored?
What is material determination?
What is Backorder processing?
What is the central organizational element in purchasing?
How is plant determined?
What is the relationship between company code and sales organization?
What is a handling unit?What is the access sequence for header conditions?
What are the highest organizational units in SD, MM, PP and FICO?
What is the functionality of negative posting in billing document?
What is mean of Rebate processing?
How is shipping point determined?
What is difference between transport and task?
What is the client specific data?
What is ABAP debugging?
How subtotal in pp is related to credit limit?
What is the difference between discount and rebate?
What are the routines?
What are the reports u have generated with help of ABAP?What are all the things we need to do configure?
What is meant by Variant Configuration?
What is the relation ship between sales organization
What are the influencing factors for account determination
What are the influencing factors for account determination
What are dependencies in variant configuration?
How alternate condition base value?
How alternate condition base value?
What is the use of pod?
What is difference between listing and exclusion?
How revenue account is determined?
When will you combine deliveries into one invoice?
How will be the Ticket process flow happens in a Production support projectWhat is transfer order?
What are the fields in pricing procedure?
What are the Standard output types in SD?
What is Condition type?
What are the issues u have faced in training?
What is difference between delivery document & scheduling?
How is item category determined?
What is Extract used in condition tech. in pricing?
What is the difference between plant and storage location?
What is the difference between item proposal
What are the statuses?
What is Lean Warehouse Management?
What is the purpose of sales document type?
What is an integration point between SD AND MM?
What are MRP types?
What is use of customer group?
What is the difference between incomplete order and backorder processing?
Why does the customer master have different views?
What is t-code for listing the blocked documents?
What is batch split?
What is Product attributes?
What is difference between SD account key and FI account key?
What is the use of pricing date in condition type?
What is the link/control between sales and distribution and quality?
What is difference between inclusive and exclusive?
How is access seq. controlled?
What does an item category control?
What is backorder processing?
What is business item?
What is Lump sum payment?
What is the advantage of using the text as a reference
What are the Steps in consignment processing?
What is the purpose of creating user exits?
What is the difference between VK11 & VK31
What is the landscape of the project?
What basic questions do they ask relating to order management?
What are 16 fields in pricing procedure?
How is storage location determined?
What is the difference between ATP check and availability check?
What is the purpose to differentiate the sales document type?
What will do in realization?
What is the importance of release status and dynamic field
What is the difference between centralized credit management
What do you mean by POD (proof of delivery)?
What is the parent and child relationship?
How to configure partial deliveries?
What is ABAP query?
How is step and counter differentiated?
What are the effects of PGI?
What is condition supplement?
What is condition exclusion?
What is the difference between alternative calcluation type
What are the Techniques in delivery scheduling?
What are the differences between billing document and invoice?
What will you do in blue print stage?
How will access the data in to production?
What is transfer order?
What is Group condition?
What is cut over strategy?
What is the relation between PGI and TOR?
How is route determined?
What is consumption based planning?
What is the relation ship between sales organization and plants?
What is Item Category Control?
What is Returnable packaging processing means?
What is IMG?
What are the Differences between invoice and billing doc?
What is the relation between sales organization and company codes?
What is Replenishment lead time?
How can we create user exits?
How can we create user exits?
Where is shipping conditions stored?
What is material determination?
What is Backorder processing?
What is the central organizational element in purchasing?
How is plant determined?
What is the relationship between company code and sales organization?
What is a handling unit?
What is the access sequence for header conditions?
What are the highest organizational units in SD, MM, PP and FICO?
What is the functionality of negative posting in billing document?
What is mean of Rebate processing?
How is shipping point determined?
What is difference between transport and task?
What is the client specific data?
What is ABAP debugging?
How subtotal in pp is related to credit limit?
What is the difference between discount and rebate?
What are the routines?
What are the reports u have generated with help of ABAP?
What are all the things we need to do configure
What is meant by Variant Configuration?
What is the relation ship between sales organization
What are the influencing factors for account determination
What are the influencing factors for account determination
What are dependencies in variant configuration?
How alternate condition base value?
How alternate condition base value?
What is the use of pod?
What is difference between listing and exclusion?
How revenue account is determined?
When will you combine deliveries into one invoice?

CREDIT MANAGEMENT

2011-06-28T17:21:00.000+05:30

CREDIT MANAGEMENT

A credit limit may be a customer's credit limit, which is the permitted limit of value of open items, such as invoices not yet paid, plus the value of open sales orders.
- The credit limit is the total combined value of the following documents:
- Net value of sales order
- Open Sales order: order created, but not delivered
- Open deliveries: delivered, but not invoiced
- Open billing doc: value of billing doc, which has not yet been forwarded to accounting
- Open items: forwarded to accounting, but not settled.

Types of Credit Check

- Simple Credit Check
- Automatic Credit Check
o Static
o Dynamic

Simple Credit Check:

SPRO- IMG- SD- Basic Functions- Credit Mgmt/ Risk Mgmt- Simple Credit Check- Assign Credit Check to Doc Types.
- Based on sales doc types
- It will check all the above-mentioned docs & if the credit limit exceeds, the system responds in the way defined by you in the configuration menu.
- Cannot differentiate according to customer

3 ways to Control the Simple Credit Check:
- A: warning
- B: error message: the doc cannot be saved
- C: warning message with delivery block: the doc can be saved but is automatically blocked for delivery.

Automatic Credit Check:

This credit mgmt control is maintained by using the automatic credit control functionality. The automatic credit control divides the sales doc types, the delivery doc types, & goods issue into specific credit groups. It also uses the customer's risk category as assigned to the CMD of the payer & assigns an outcome proc to the combination of the above 2 objects, i.e. the credit group & customer risk category along with the credit control area. The definition of customer's risk category is carried out in the fin accounting module.
A customer's risk category is a grouping category that controls the credit check when automatic credit control takes place. Thus one can assign high-risk customers to risk category for e.g. A01, medium risk to B01 and low risk to C01.

Automatic credit check divides customers in to 3 categories:
- High-risk customers,
- Low risk customers &
- Medium risk customers.

A credit check can only occur at 3 places: Credit Group
- Sales order: for high risk customers
- Delivery: for medium risk customers
- Goods Issue: for low risk customers

Credit Control Area (CCA): highest organizational element in credit management. A credit control area is an organizational unit that is comprised of one or more company codes. A company code can have no more than one credit control area. Defined by FI.

Menu Path to create Credit Control Area: OB45: FI people.

SPRO- IMG- Enterprise Stru- Definition- Fin Accounting- Define Credit Control Area
Credit Control Area Description
0001 Credit control area 0001
1000 Credit control area Europe

Menu Path to Assign Company Code to Credit Control Area: OB38: FI people.
SPRO- IMG- Ent Stru- Assignment- Fin Accounting- Assign Comp Code to CCA
- It is possible to assign Credit Control Area to a Sales Area. This is more specific assignment than the assignment to Company Code.
Company code Company name City Credit Control Area Over write CCA

Menu Path for Defining Risk Categories: OB01: FI people

SPRO- IMG- Fin Accounting- Account Receivables & Payables- Credit Mgmt- Credit Control Account-

Define Risk Categories.

Risk Category CCA Name
001 4500 Low risk
002 4500 Medium risk
003 4500 High risk

Menu Path for defining Credit Groups: OVA6

SPRO- IMG- SD- Basic Function- Credit Mgmt/ Risk Mgmt- Credit Mgmt:
- Define Credit Groups: OVA6
- Assign Credit Groups to Sales Doc's & Delivery Doc's
o Credit Limit check for Order Types: OVAK
o Credit Limit check for Delivery Types: OVAD
- Define Automatic Credit Control: OVA8
Define Credit Croups: OVA6

One merely creates a credit group for each differentiation in the doc type. You enter the credit groups when you configure the sales doc types for credit management & define the automatic credit check. The following credit groups are contained in the standard R/3 system:
- 01: credit group for sales order
- 02: credit group for delivery
- 03: credit group for goods issue

CG (Credit Group) Doc Credit Group
01 Credit group for sales order
02 Credit group for delivery
03 Credit group for goods issue

Assign Sales Documents & Delivery Documents:

Sales Doc Type Descp Check Credit Credit Group
OR Std Order D 01

Delivery Type Descp Del Credit Group GI Credit Group

LF Delivery 02 03 - automatic credit check should be carried out.
- Specify a Credit Group
- Specify a Credit Group for the Delivery Type for which you want to carry out a credit check
- Specify a Goods Issue Credit Group for the Delivery Type for which a credit check is to be carried out for goods issue.
- SIMPLE CREDIT CHECK CANNOT BE ASSIGNED TO DOCUMENTS.

Define Automatic Credit Control:
One can now assign settings to the combination of the Credit Control Area, the Customer Risk Category & the Credit Group.

CCA Risk Cat Credit Group Credit Control
4500 001 01 Low risk sales orders
4500 001 02 Low risk deliveries
4500 001 03 Low risk goods issue
4500 002 01 Medium risk sales orders
4500 002 02 Medium risk deliveries
4500 002 03 Medium risk goods issue
4500 003 01 High risk sales orders
4500 003 02 High risk deliveries
4500 003 03 High risk goods issue

Select line item and go to details, you can decide whether to do Static or Dynamic Credit Check. Credit Horizon can also assigned here. Additional function checks can be performed here:
- A credit check when the maximum document value is exceeded.
- A credit check when changing critical fields.

The risk category assignment occurs in the same place as the customer's credit limit, which is the customers credit management screen. That is, the risk category is assigned to the customer by the Finance in transaction code FD32.

The customer credit master record is divided in to 5 views:
- Overview Screen: gives an overview of credit settings in relation to the customer, including his credit limit, credit exposure, the %tage of credit limit used, his payment data & his risk category.
- Address: view gives the customers address details as they appear in CMD
- Central Data: is a view that shows the total credit limit the customer can receive across all credit control areas as well as the maximum limit he can receive in one credit control area.
- Status: view shows the customer's actual individual details according to particular CCA being investigated. This includes his credit limit, percentage used, credit exposure, risk category, whether he is blocked due to credit or not.
- Payment history: view displays the payments made by the customer for a particular credit control area where a comp code is assigned.

Static Credit Check Dynamic Credit Check
Net Doc Value Net Doc Value
Open Order Open Order
Open Delivery Open Delivery
Open Billing Open Billing
Open Item Open Item

Compares the total combined values of the above-mentioned documents to credit limit. Plus credit horizon. Compares the values of the following documents to credit limit + credit horizon.
Credit horizon has an attached time period that states that the system is not to include sales orders in the total of outstanding items created after that specified period i.e. for the purpose of evaluating credit, you want the system to ignore all open orders that are due for delivery after the horizon date. Maintained for low & medium risk customers.

Update Groups

Basically it is a info structure where system stores all the data about credit limit. The credit relevant data is updated in a info structure, where it is accessed & updated. Thus each automatic credit control must be assigned an update group.
- Update Group 000012
- Update Group 000015: delivery & billing
- Update Group 000018: sales order, delivery & billing.

Update group 000012, updates at:
- Sales doc: increased order value
- Delivery: decreased order value & increased delivery value
- Billing: decreased delivery value & increased billing amount
- Invoice: decreased billing amount & increased open item value.

Release Blocked Sales Order/ Deliveries:
- VKM3: sales order
- VKM5: delivery
- VKM4: both

One can see the offending document. Note on the right hand side, the 'Status Field'. This shows the check, the doc failed. If this field is empty, the doc did not fail a credit check, even though it may be in the list of SD documents that are "required to be released".
To release the doc, one indicates the doc to be released and then clicks on the 'Release Button'. The result is the offending doc entry, highlighted green. One then proceeds to save, after which you are informed the doc number has been released.
- Net value with sub total 'A', in pricing proc, will be the basis for credit limit.

Copy Control Settings Screenshots

2011-06-21T12:08:00.000+05:30

BELOW ARE THE SCREENSHOTS OF THE COPY CONTROL SETTINGS AT HEADER LEVEL, ITEM LEVEL, AND SCHEDULE LINE LEVEL

CLICK ON SCREENS TO VIEW A LARGER SCALE

Master Data Tables

2011-06-15T13:51:00.000+05:30

General settings

Countries
T005 Countries
Currency
TCURC Currency codes
TCURR Wisselkoersen
TCURT Currency name
TCURX Decimal places for currencies.
Unit of measure
T006 Units of measure
Calendar functions
T247 Month names
TFACD Factory calendar definition
T015M Month names
TTZZ Time zones
TTZD Summer time rules
TTZDF Summer time rules (fixed annual dates)
TTZDV Summer time rules (variable dates)
TTZDT Summer time rules texts
TTZ5 Assign Time Tones to Countries
TTZ5S Assign time zones to regions
Enterprise structure
Definition
FI T880 Company
T001 Company code
CO TKA01 Controlling area
LO T001W Plant / sales organisation
T499S Locations
TSPA Division
SD TVKO Sales organisation / company code
TVTW Distribution channel
TVBUR Sales office
TVKBT Sales office text
TVKGR Sales group
TVGRT Sales group text
T171T Sales district text
MM T001L Storage locations
T024E Purchasing organization
T3001 Warehouse number
TVST Shipping point
TVLA Loading point
TTDS Transportation
Assignment
CO TKA02 Assign company code to controlling area
LO T001K Assign plant (valuation area) to company code

SD TVKO Sales organisation / company code
TVKOV Distribution channel / sales organisation
TVKOS Division to sales organization
TVTA Sales aria
TVKBZ Sales office to sales area
TVBVK Sales group to sales office
TVKWZ Plants to sales organization
MM T024E Purchasing organization / company code
T024W Plant to Purchase organization
T001K Link plant ( = valuation area) / company code
TVSWZ Shipping point to plant
T320 Assignment MM Storage Location to WM Warehouse
Financial accounting
Company code
T004 Chart of accounts
T077S Account group (g/l accounts)
T009 Fiscal year variants
T880 Global company data
T014 Credit control area
Fi document
T010O Posting period variant
T010P Posting Period Variant Names
T001B Permitted Posting Periods
T003 Document types
T012 House banks

Not categorized
T007a Tax keys
T134 Material types
T179 Materials: Product Hierarchies
T179T Materials: Product hierarchies: Texts
TJ02T Status text
TINC Customer incoterms
TVFK Billing doc types
T390 PM: Shop papers for print control

Basic data / administration
Workbench related tables
Data dictionary tables
DD02L Tables in SAP
DD02T Tables description
DD03L Field names in SAP
DD03T Field description in SAP
Workbench
TADIR Directory of R/3 Repository Objects
TRDIR System table TRDIR
TFDIR Function Module
TLIBG Person responsible for function class
TLIBT Function Group Short Texts
TFTIT Function Module Short Text
TSTC Transaction codes in SAP
TSTCT Transaction codes texts
T100 Message text (vb e000)
VARID Variant data
D020T Screen texts
TDEVC Development class
TDEVCT Texts for development classes
Administration
User administration
USR01 User master
USR02 Logon data
USR03 User address data
USR04 User master authorizations
USR11 User Master Texts for Profiles (USR10)
UST12 User master: Authorizations
USR12 User master authorization values
USR13 Short Texts for Authorizations
USR40 Prohibited passwords
TOBJ Objects
TOBC Authorization Object Classes
TPRPROF Profile Name for Activity Group
DEVACCESS Table for development user
Batch input queue
APQD DATA DEFINITION Queue
APQI Queue info definition
Job processing
TBTCO Job status overview table
TBTCP Batch job step overview
Spool
TSP02 Spool: Print requests
Runtime errors
SNAP Runtime errors
Message control
TNAPR Processing programs for output
NAST Message status
NACH Printer determination
EDI
EDIDC Control record
EDIDD Data record
EDID2 Data record 3.0 Version
EDIDS EDI status record
EDPAR Convert External < > Internal Partner Number
EDPVW EDI partner types
EDPI1 EDI partner profile inbound
EDPO1/2/3 EDI partner profile outbound
Change documents
CDHDR Change document header
CDPOS Change document positioned
JCDS Change Documents for System/User Statuses (Table JEST)
Reporting tree table
SERPTREE Reporting: tree structure
LIS structure/control tables
TMC4 Global Control Elements: LIS Info Structure

MASTER DATA:
Material master:
MARA Material master
MAKT Material text
MARC Material per plant / stock
MVKE Material master, sales data
MARD Storage location / stock
MSKA Sales order stock
MSPR Project stock
MARM Units of measure
MEAN International article number
PGMI Planning material
PROP Forecast parameters
MAPR Link MARC <=> PROP
MBEW Material valuation
MVER Material consumption
MLGN Material / Warehouse number
MLGT Material / Storage type
MPRP Forecast profiles
MDTB MRP table
MDKP Header data for MRP document
MLAN Tax data material master
MTQSS Material master view: QM
Basic data text (sap script)
STXB SAP script: Texts in non-SAP script format
STXH STXD SAP script text file header
STXL STXD SAP script text file lines
Batches
MCHA Batches
MCH1 Batches
MCHB Stock: batches
Customer master data
KNA1 Customer master
KNB1 Customer / company
KNVV Customer sales data
KNBK Bank details
KNVH Customer hierarchy
KNVP Customer partners
KNVS Shipment data for customer
KNVK Contact persons
KNVI Customer master tax indicator
Vendor
LFA1 Vendor master
LFB1 Vendor per company code
LFB5 Vendor dunning data
LFM1 Purchasing organization data
LFM2 Purchasing data
LFBK Bank details

Customer – material info record
KNMT Customer material info record
Bank data
BNKA Master bank data
Characteristics:
CABN Characteristics ( o.a. batch/vendor)
CABNT Characteristics description
CAWN Characteristics ( o.a. material)
CAWNT Characteristics description
AUSP Characteristic Values
Class types and objects :
TCLAO Several class types for object
TCLA Class types ( vb. lfa1 => v10 en 010)
TCLAT Class type text
TCLT Classifiable objects
TCLC Classification status
Links:
INOB Link between Internal Number and Object
KLAH Class header data
KSSK Allocation Table: Object (vb.matnr) to Class
KSML Characteristics for a class (internal number)
FI/CO :
FI :
Master data
SKA1 Accounts
BNKA Bank master record
Accounting documents // indices
BKPF Accounting documents
BSEG item level
BSID Accounting: Secondary index for customers
BSIK Accounting: Secondary index for vendors
BSIM Secondary Index, Documents for Material
BSIP Index for vendor validation of double documents
BSIS Accounting: Secondary index for G/L accounts
BSAD Accounting: Index for customers (cleared items)
BSAK Accounting: Index for vendors (cleared items)
BSAS Accounting: Index for G/L accounts (cleared items)
Payment run
REGUH Settlement data from payment program
REGUP Processed items from payment program
CO :
TKA01 Controlling areas
TKA02 Controlling area assignment
KEKO Product-costing header
KEPH Cost components for cost of goods manuf.
KALO Costing objects
KANZ Sales order items - costing objects
Cost center master data
CSKS Cost Center Master Data
CSKT Cost center texts
CRCO Assignment of Work Center to Cost Center
Cost center accounting
COSP CO Object: Cost Totals for External Postings
COEP CO Object: Line Items (by Period)
. COBK CO Object: Document header
COST CO Object: Price Totals
Sales and Distribution (SD) :

VBFA Document flow (alg.)
VTFA Flow shipping documents
Sales order :
VBAK Header data
VBAP Item data
VBPA Partners in sales order
VBKD Sales district data
VBEP Data related to line items, delivery lines
Billing document :
VBRK header data
VBRP Item data
Shipping :
VTTK Shipment header
VTTP Shipment item
VTTS Stage in transport
VTSP Stage in transport per shipment item
VTPA Shipment partners
VEKP Handling Unit - Header Table
VEPO Packing: Handling Unit Item (Contents)
Delivery :
LIKP Delivery header
LIPS Delivery item
Pricing :
KONH Conditions header
KONP Conditions items
KONV Procedure ( billing doc or sales order)
KOND
contracts :
VEDA Contract data
Material Management (MM) :
Material document
MKPF material document
MSEG material document (item level)
Purchasing
EKKO Purchase document
EKPO Purchase document (item level)
EKPV Shipping-Specific Data on Stock Tfr. for Purch. Doc. Item
EKET Delivery schedule
VETVG Delivery Due Index for Stock Transfer
EKES Order Acceptance/Fulfillment Confirmations
EKKN Account assignment in purchasing
EKAN Vendor address purchasing
EKPA Partner functions
EIPO Item export / import data
EINA Purchase info record (main data)
EINE Purchase info record (organisational data)
EORD Source list
EBAN Purchase requisition
EBKN Purchase Requisition Account Assignment

Warehouse Management (WM) :
Transfer requirement
LTBK Transfer requirement - header
LTBP Transfer requirement - item
Transfer order
LTAK Transfer order - header
LTAP Transfer order - item
Master data - stock positions
LQUA Quants
Inventory documents in WM
LINK Inventory document header
LINP Inventory document item
LINV Inventory data per quant
Quality Management (QM) :
Inspection lot / info record
QALS Inspection lot record
QAMB Link inspection lot - material document
QAVE Inspection usage decision
QDPS Inspection stages
QMAT Inspection type - material parameters
QINF Inspection info record (vendor - material)
QDQL Quality level
QDPS Inspection stages
Quality notification
TQ80 Notification types
QMEL Quality notification
QMFE Quality notification – items
QMUR Quality notification – causes
QMSM Quality notification – tasks
QMMA Quality notification – activities
QMIH Quality message - maintenance data excerpt
Certificate profile
QCVMT Certificate profile characteristic level: texts
QCVM Certificate profile characteristic level
QCVK Certificate profile header

Production Planning (PP)
Work center
CRHH Work center hierarchy
CRHS Hierarchy structure
CRHD Work center header
CRTX Text for the Work Center or Production Resource/Tool
CRCO Assignment of Work Center to Cost Center
KAKO Capacity Header Segment
CRCA Work Center Capacity Allocation
TC24 Person responsible for the workcenter
Routings/operations
MAPL Allocation of task lists to materials
PLAS Task list - selection of operations/activities
PLFH Task list - production resources/tools
PLFL Task list - sequences
PLKO Task list - header
PLKZ Task list: main header
PLPH Phases / suboperations
PLPO Task list operation / activity
PLPR Log collector for tasklists
PLMZ Allocation of BOM - items to operations
Bill of material
STKO BOM - header
STPO BOM - item
STAS BOMs - Item Selection
STPN BOMs - follow-up control
STPU BOM - sub-item
STZU Permanent BOM data
PLMZ Allocation of BOM - items to operations
MAST Material to BOM link
KDST Sales order to BOM link
Production orders
AUFK Production order headers
AFIH Maintenance order header
AUFM Goods movement for prod. order
AFKO Order header data PP orders
AFPO Order item
RESB Order component
AFVC Order operations
AFVV Quantities/dates/values in the operation
AFVU User fields of the operation
AFFL Work order sequence
AFFH PRT assignment data for the work order(routing)
JSTO Status profile
JEST Object status
AFRU Order completion confirmations
PRT’s voor production orders
AFFH PRT assignment data for the work order
CRVD_A Link of PRT to Document
DRAW Document Info Record
TDWA Document Types
TDWD Data Carrier/Network Nodes
TDWE Data Carrier Type
Planned orders
PLAF Planned orders
KANBAN
PKPS Kanban identification, control cycle
PKHD Kanban control cycle (header data)
PKER Error log for Kanban containers
Reservations
RESB Material reservations
RKPF header
Capacity planning
KBKO Header record for capacity requirements
KBED Capacity requirements records
KBEZ Add. data for table KBED (for indiv. capacities/splits)
Planned independent requirements
PBIM Independent requirements for material
PBED Independent requirement data
PBHI Independent requirement history
PBIV Independent requirement index
PBIC Independent requirement index for customer req.

Project system (PS)
Basic data
PRHI Work Breakdown Structure, Edges (Hierarchy Pointer)
PROJ Project definition
PRPS WBS (Work Breakdown Structure) Element Master Data

RPSCO Project info database: Costs, revenues, finances
MSPR Project stock

Equipment
EQUI Equipment master data
EQKT Equipment short text
EQUZ Equipment time segment

Plant maintenance (PM)
IHPA Plant Maintenance: Partners
OBJK Plant Maintenance Object List
ILOA PM Object Location and Account Assignment
AFIH Maintenance order header
Human resources
Settings
T582A Infotypes: Customer-Specific Settings
Master data
T527X Organizational Units
T528T Position Texts
T554T Attendance and Absence Texts
T501 Employee group
T503 Employee group, subgroup
T503K Employee subgroup
T510N Pay Scales for Annual Salaries (NA)
T549A Payroll Accounting Areas
T750X Vacancy
Infotypes
PA0001 Org. Assignment
PA0002 Personal Data
PA0006 Addresses
PA0007 Planned Working Time
PA0016 Contract elements
PA0008 Basic pay
PA0105 Communications
PA1007 Vacancies
PA1035 Training
PA2001 Absences

Other important table

JEST System Status with object number
TJ02 System status description.

MRP Related

MDKP Header Data for MRP Document
MDTB MRP Table
MDVL Planning file entry for long term planning
MDVM Enry in MRP file
PBVPV Material Index for consumption of planning
REUL Material stock transfer reservation index
SAFK Run schedule master data
SQ01 Abap query
EDMSG ALE message type table
EDI Specific Transactions
• VOE1 Translation between EDI categories and SD item categories
• VOE2 Table EDSC view. Customer link to sales area detail
• VOE3 Table view EDPVW. Add partner types that will be transferred to the IDoc
• VOE4 Table view EDPAR. Link external partner number with our internal number
• WEDI EDI Administrator Menu
• BALE Idoc Administration
Scheduling agreements
• OVA9 Create entries for each sold-to customer for which you will receive EDI schedule releases. At implementation, the only field that needs to be maintained is "Check PO number," which causes SAP to make sure that the PO number sent on the release matches the PO number on the schedule agreement. This transaction updates table T663A. SAP will not post an EDI schedule release, if this record is missing.
• OVAI Create entries for each Vendor / Partner description combination. (Vendors must match sold-to Acct. at Cust., and Partner descriptions must match ship-to Partner descriptions.) This transaction updates table T661W. SAP uses this table to determine the schedule agreement sold-to partner.
• OVAJ If you would like SAP to post schedule requirements using discrete dates only, instead of weekly and/or monthly buckets, you can indicate the days of the week that you deliver to this customer. SAP will divide the customer's quantity for a week or month evenly into the days of the week specified by the distribution function code. This code must be sent in the DELINS IDoc in field E1EDP16-ETVTF.
IDoc Transactions
• WE09 / WE02 IDoc lists according to content. View IDocs via specific IDoc number or business application detail contained within the contents of a segment.
• WE05 View IDocs
• WE19 EDI test tool. Use to test inbound Function module changes.
• WE20 Partner profile configuration. Add partner detail together with inbound and outbound relationships. We also incorporate message control on the outbound IDocs. Utilize the organizational units to trap functional errors for further processing
• WE30 Create IDoc extension type
• WE31 Segment create
• WE57 Assign function module to logical message and IDoc type
• WE60 IDoc type documentation tool
• WE82 Link Release detail to Extension IDoc Type
• BD55 Conversion rule user exit. Link conversion rule user exit to the different system \ partner combinations
• BD87 Reprocess IDocs in error or waiting for action. (Both inbound and outbound in 4.6. Use BD88 in prior versions)
• BALA ALE Application Distribution
• BALM ALE Master Data Distribution
Output determination
856 - ASN
• V/36 Maintain output determination for deliveries (Output determination procedures). V10000 (Header output) has condition type LAVA (usually with requirement 1 NB: Use V/84 ? V7ALLE ? SHAD for grouped ASNs. I.e. Group deliveries into shipments
• VV21,VV22,VV23 Create output condition records for shipping. LAVA ? WE (Partner function) - We must add each new partner with VV21
• VL71 Reissue output for deliveries
810 - Invoice
• V/54 Maintain access sequence for billing documents
• VV31,VV32,VV33 Create condition records for billing documents. (RD00 ? RE Billing party)
• VF31 Reissue output for billing documents
855 ? Order Response
• V/30 Sales document output types (BA00)
• V/48, V/32, V/43 Maintain access sequence for sales documents
• VV11,VV12,VV13 Create condition records for sales documents. (BA00 ? SP Sold to party)
Requirements coding
• V/27 Create code to check requirements for output control. Used to check ZBA0 against BA00 output.
Sales & Distribution
Sales order / Quote / Sched Agreement / Contract
• VA02 Sales order change
• VA05 List of sales orders
• VA22 Quotation change
• VA32 Scheduling agreement change
• VA42 Contract change
Billing
• VF02 Change billing document
• VF11 Cancel Billing document
• VF04 Billing due list
• FBL5N Display Customer invoices by line
• FBL1N Display Vendor invoices by line
Delivery
• VL02N Change delivery document
• VL04 Delivery due list
• VKM5 List of deliveries
• VL06G List of outbound deliveries for goods issue
• VL06P List of outbound deliveries for picking
• VL09 Cancel goods issue
• VT02N Change shipment
• VT70 Output for shipments
General
• VKM3, VKM4 List of sales documents
• VKM1 List of blocked SD documents
• VD52 Material Determination
Workflow
• SWEAD Event queue administration
• SWE2 Event type linkages
• SWE3 Event linkages
• PPOME Organizational Unit Maintenance
• SWE5 Consistency Checks for Event Linkages
• SWUD Workflow Diagnostic Tool
General
The following section provides detail on other useful SAP areas.
Create delivery via transfer orders
Once the order is saved proceed through the following steps. The process assumes the item has values in the warehouse bin.
• VL04 Delivery due list. Run the delivery due with your order number to create the delivery
• LT03 Create Transfer Order. EG. Warehouse: 101 and enter. Picking background. Save
The Transfer order should now be saved. It now needs to be confirmed.
• In LT03 go to menu option Transfer Order -> Confirm ? Transfer Order
• Enter
• Save
The transfer order is now confirmed.
• VL02N Delivery change. EG: Edit the delivery to do the following Pack ? External customer material number = COO. External delivery number ? Waybill number. BOL ? Transport tag. Carrier ? Header partner ? SP (E.G. FXP). Tracking number = Packing Unit
Purchase Orders
• ME22N POChange
• ME57 Create POfrom purchase requisition
ATP
• CO09 Availability overview
Goods Movement
• MIGO Post goods receipt
• MB51 Material document list
• MB01 Goods Movement
Other
• MD04 Material Requirements. Shows material requirements and releases against materials
• SE38 ABAP Editor. Used to modify ABAP programs
• SM01 Transaction list. Lock transactions in the system. Also a good tool to see what transactions are available
• SHDB Transaction recorder (BDC)
• CMOD User exit \ project tool. Coordinates your changes into projects for the purpose of activating all user exits for a particular project. A user exit needs to be modified before it will work
• SE16 Table contents display
• SOST View mails sent externally from SAP
• SU53 Check authorization object
• SQVI Table Quickviewer ? Used to created quick client dependent reports
• ST22 ABAP Dump Analysis
• ST01 System trace
• ST11 Display developer trace
• ST05 SQL Trace
• SM21 System log
• ST22 Display short dumps
• SM12 Display locked entries
Programs
• List of ABAP Reports
Idoc
• RBDAPP01 Post inbound Idocs to application documents
• RBDAGAI2 Re-processing of IDocs after ALE input error
• RBDAGAIE Reprocessing of edited IDocs
• RBDMANIN Start error handling for non-posted Idocs
• RSEINB00 Idoc inbound processing by file
• RSEOUT00 Process outbound IDocs

Simplify......SAP_SD: Make-to-Order__Process Flow

2011-06-10T12:41:00.000+05:30

Simplify......SAP_SD: Make-to-Order__Process Flow: "Materials in SAP ECC system is usually either procured or produced and kept in stock or it is custom made as per the customer’s specificatio..."

SAP Note 11162 - Invoice split criteria in billing document .

2011-06-03T19:00:00.000+05:30

Symptom

From a number of deliveries or sales orders more than one billing document is created.

Cause and prerequisites
The invoice split may have been carried out for the following reasons:

a) Explicit setting in Customizing
b) Different header partners
c) Different header fields
d) The billing date of all documents is equated in a data transfer routine (for example, by VBRK-FKDAT = SY-DATUM). This works when you are billing using VF01; a single billing document is generated. However, if you use VF04 or in case of a batch, several billing documents might be generated.

Solution

Please check the causes mentioned above:

1. Explicit setting in Customizing:
On the detail screen of the document flow table (TVCPF) in the entry field 'DATEN VBRK/VBRP' (as of Rel.2.2..: 'Data transfer') the routine '003' (single invoice) was entered and thus an invoice split was created.
2. Different header partners
The header partners in the billing documents created are not identical which causes an invoice split. With regard to partner processing, an invoice split also occurs if the entries in the partner table of the reference document and the billing document also differ only in one field (!) for the partner functions of the billing document header (in the standard system, these are SP, BP and PY).
3. Different header fields
The header fields in the billing documents created are not identical which causes an invoice split.
Attention: Not all header fields in the billing document are visible on the header detail screen of the billing document.
4. When using transaction VF04 or Billing (background) the date of the billing document (e.g. the current date) must be entered (In VF04: settings, default data. In VF06 or background: variant with parametrization) to avoid an unwanted split due to the billing date.
5. To avoid a split due to different header fields - except for the fields listed above - you have the option of using customer-specific data transport routines in the copying control of the relevant document types which initialize the corresponding fields. However, the information contained in these fields is then lost in the billing document.

LF Delivery without Sales Order !!

2011-05-28T18:53:00.000+05:30

STRANGE BEHAVIOR IN SAP : From sdn forum :

Ideally if Delivery document type is with sales order requirement system should not allow to created delivry without sales order BUT there is one possibility to manipulate this check.
You can check following scenario yourself in Ides or test system

Create one sales order using VA01
Create delivery with reference to sales order before saving delete all items from delivery and enter same items again. and save the delivery.

Now go to VL02n and check the document flow of that delivery. you will find sales order reference missing.

It looks like delivery type LF is created without reference to sales order.
And if you check the document flow of sales order it show no reference delivery is created.

Actually once you delete items form delivery all the references also gets deleted and then you can enter not only same material but can enter any material, any quantity and you can do PGI and billing also, system will not stop you anywhere but you can not find the reference sales order.

This behaviour is strange and I am also trying to find the solution to restrict item deletion from delivery doc.

Regards
Mayank sdn forum ( http://forums.sdn.sap.com/thread.jspa?threadID=987920 )

SAP MM : A Few tables for reference

2011-05-26T17:45:00.001+05:30

Material Master Tables

General Material Data – MARA
Material Descriptions – MAKT
Plant Data for Material – MARC
Material Valuation – MBEW
Storage Location Data for Material – MARD
Units of Measure for Material – MARM
Sales Data for Material – MVKE
Forecast Parameters – MPOP
Planning Data – MPGD_MASS
Tax Classification for Material – MLAN
Material Data for Each Warehouse Number – MLGN
Material Data for Each Storage Type – MLGT
Vendor Master Tables:
Description – Table
Vendor Master (General Section) – LFA1
Vendor Master (Company Code) – LFB1
Vendor master (VAT registration numbers general section) – LFAS
Vendor master (dunning data) – LFB5
Vendor Master (Bank Details) – LFBK
Vendor master record (withholding tax types) X – LFBW
Vendor master record purchasing organization data – LFM1
Vendor Master Record: Purchasing Data – LFM2
Vendor Subrange – WYT1
Vendor Sub-Range Description – WYT1T
Partner Functions - WYT3
Related to Materials:
MARA - Material Master: General data
MAKT - Material Master: Description
MARM - Material Master: Unit of Measure
MAPE - Material master: Export control file
MARC - Material master: Plant data
MARD - Material master: Storage location
MAST - Material link to BOM
MBEW - Material valuation
MLGN – Material Master: WM Inventory
MLGT – Material Master: WM Inventory type
MDIP - Material: MRP profiles (field contents)
MKOP - Consignment price segment (old versions of SAP)
EBEW - Valuation of sales order stock
QBEW - Valuation of project stock
MVER – Material Master: Consumption
DVER – Material Master: Consumption
MVKE – Material Master: Sales
MLAN - Material Master: Tax indicator
MARC - Material Master: Plant data
MAPR – Material Master: Forecast
MARD – Material Master: Storage Location
MCH1 – Material Master: X Plant Batches
MCHA – Material Master: Batches
MCHB – Material Master: Batch Stock
MDMA - MRP Area data
DBVM - MRP Planning File Entry: MRP Area
MOFF - Outstanding Material Master Records (Maintenance status)
MARCH - Material Master C Segment: History
MARDH - Material Master Storage Location Segment: History
MBEWH - Material Valuation: History
MCHBH - Batch Stocks: History
MKOLH - Special Stocks from Vendor: History
MSCAH - Sales Order Stock at Vendor: History
MSKAH - Sales Order Stock: History
MSKUH - Special Stocks at Customer: History
MSLBH - Special Stocks at Vendor: History
MSPRH - Project Stock: History
MSSAH - Total Sales Order Stocks: History
MSSQH - Total Project Stocks: History
Related to Vendors:
LFA1 - Vendor Master: General data
LFB1 - Vendor Master: Company data
LFM1 - Vendor Master: Purchasing Data (Purchasing organization)
LFM2 - Vendor Master: Purchasing Data (Plant, Vendor sub-range)

Related to Purchasing:
EBAN - Purchase requisition: items
EBKN - Purchase Requisition: account assignment
STXH - SAPScript Text Header
STXL - SAPScript Text Lines
EKKO - Purchasing document header
EKPO - Purchasing Document: Item
EKET - Purchasing Document: Delivery Schedules
MDBS - Material View of Order Item/Schedule Line (good to find open PO's)
EKKN - Account assignment in purchasing document
EORD - Purchasing Source List
EIPA - Order price history record
EKAB - Release documentation
EKBE - Purchasing document history
EKBZ - Purchasing document history: delivery costs
EKPB - "Material to be provided" item in purchasing document
ESKL - Account assignment specification for service line
ESKN - Account assignment in service package
ESLH - Service package header data
ESLL - Lines in service package
ESSR - Service entry sheet header data
ESUC - External services management: Unplanned limits for contract item
ESUH - External services management: unplanned service limits header data
ESUP - External services management: unplanned limits for service packages
ESUS - External services management: Unplanned limits for service types
EINA - Purchase Info Record: General
EINE - Purchasing info record: purchasing organization data
KONP - Condition Item
KONH - Condition Header
Related to Inventory Management:
ISEG - Physical inventory document items
MKPF - Material document: Header
MSEG - Material document: item
RKPF - Reservation: Header
RESB - Reservation: Item
Related to Invoice Verification
BSIM - Secondary index: documents for material
MYMFT - FIFO results table
MYML - LIFO material layer
MYMLM - LIFO material layer (monthly)
MYMP - LIFO period stocks, single material
MYMP1 - Receipt data LIFO/FIFO valuation
MYPL - LIFO pool layer
MYPLM - LIFO pool layer (monthly)
RBCO - Document item, incoming invoice account assignment
RBDIFFKO - Invoice Verification: conditions
RBDIFFME - Invoice Verification: quantity differences
RBDRSEG - Invoice Verification batch: invoice document items
RBKP - Document header: incoming invoice
RBKPB - Invoice document header (batch invoice verification)
RBTX - Taxes:incoming invoice
RBVD - Invoice document: summarization data
RBVDMAT - Invoice Verification: summarization data, material
RBWT - Withholding tax:incoming invoice
RKWA - Consignment withdrawals
RSEG - Document item, incoming invoice
Related to Customising and Other Master Data:
MDLV - MRP Areas
MDLG - MRP Areas - Storage Locations
MDLW - MRP Areas - Plants
MDLL - MRP Areas - Subcontractor
T023 - Material Groups
T024 - Purchasing groups
T030 - Standard Accounts Table (Automatic Account Determination)
T156 - Movement Type
T156T - Movement Type: Text
AUSP - Release Procedure: Strategy values (cl20n, cl24n)
AGR_USERS - Assignment of roles to users
CDHDR & CDPOS - Change history of master data and documents
EDID4 - EDI information
TSTC - SAP Transaction Codes, lock/unlock: sm01, created: se93
TSTCT - Transaction codes TEXT

SD Key TRANSACTION CODES

2011-05-26T17:18:00.003+05:30

The most frequently used transaction codes are as follows:
1. VS00 - Master data
2. VC00 - Sales Support
3. VA00 - Sales
4. VL00 - Shipping
5. VT00 - Transportation
6. VF00 - Billing

Others as follows:
At Configuration:
1. VOV8 - Define Sales documents type (header)
2. OVAZ - Assigning Sales area to sales documents type
3. OVAU - Order reasons
4. VOV4 - Assign Item categoreies(Item cat determination)
5. VOV6 - Scedule line categories
6. OVAL - To assign blocks to relevant sales documents type
7. OVLK - Define delivery types
8. V/06 - Pricing
9. V/08 - Maintain pricing procedure
10.OVKP - Pricing proc determination
11.V/07 - Access sequence

Enduser:
1. Customer Master Creation-VD01 and XD01 (for full inclu company code)
VD02 - Change Customer
VD03 - Display Customer
VD04 - Customer Account Changes
VD06 - Flag for Deletion Customer
XD01 - Create Customer
XD02 - Modify Customer
XD03 - Display Customer
2. Create Other material ----MM00
3. VB11- To create material determination condition record
4. CO09- Material availability Overview
5. VL01 - Create outbound delivery with ref sales order
6. VL04 - Collective processing of delivery
7. VA11 - Create Inquiry
VA12 - Change Inquiry
VA13 - Display Inquiry

Sales & Distribution

Sales & Distribution
Sales order / Quote / Sched Agreement / Contract
- VA01 - Create Order
- VA02 - Change Order
- VA03 - Display Order
- VA02 - Sales order change
- VA05 - List of sales orders
- VA32 - Scheduling agreement change
- VA42 - Contract change
- VA21 - Create Quotation
- VA22 - Change Quotation
- VA23 - Display Quotation

Billing
- VF02 - Change billing document
- VF11 - Cancel Billing document
- VF04 - Billing due list
- FBL5N - Display Customer invoices by line
- FBL1N - Display Vendor invoices by line

Delivery
- VL02N - Change delivery document
- VL04 - Delivery due list
- VKM5 - List of deliveries
- VL06G - List of outbound deliveries for goods issue
- VL06P - List of outbound deliveries for picking
- VL09 - Cancel goods issue
- VT02N - Change shipment
- VT70 - Output for shipments

General
- VKM3, VKM4 - List of sales documents
- VKM1 - List of blocked SD documents
- VD52 - Material Determination 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 groupSales 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 ListQuotation
VA21 Create Quotation
VA22 Change Quotation
VA23 Display Quotation
VA25 Quotations List
VA26 Collective Processing for QuotationsContract
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.ContractsItem Proposal
VA51 Create Item Proposal
VA52 Change Item Proposal
VA53 Display Item Proposal
VA55 List of Item Proposals
VA88 Actual Settlement: Sales OrdersDelivery (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 DeliveryCustomer 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 ChangePricing
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 TableBOM
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

Important Tables : SAP SD

2011-05-24T16:08:00.001+05:30

Customers

KNA1 General Data
KNB1 Customer Master–CCode Data (payment method, recon. acct)
KNB4 Customer Payment History
KNB5 Customer Master – Dunning info
KNBK Customer Master Bank Data
KNKA Customer Master Credit Mgmt.
KNKK Customer Master CCA Data (credit limits)
KNVV Sales Area Data (terms, order probability)
KNVI Customer Master Tax Indicator
KNVP Customer master partner Function
KNVD Output type
KNVS Customer Master Ship Data
KLPA Customer/Vendor Link
V_THIT Customer Hierarchy Types
KNVH Customer Hierarchies
KNVK Customer master Contact partner

Sales Documents

VBAKUK VBAK + VBUK
VBUK Header Status and Administrative Data
VBAK Sales Document – General Header Data
VBKA Sales Activities
VBKD Sales Document - Business Header/Item Data
VBPA Sales Document - Partners Header Data
VBUP Item Status
VBPA Sales Document – Partner Item Data
VBAP Sales Document – General Item Data
FPLA sales Document – Items Conditions data
VBFA Document Flow
VBEP Sales Document Schedule Line
VBBE Sales Requirements: Individual Records
VEDA Sales Contract Data
VBELN Sales and Distribution Document Number

SD Delivery

LIPS Delivery Document item data, includes refer. PO
LIKP Delivery Document Header data
Billing Document
VBRK Billing Document Header
VBRP Billing Document Item
Pricing Document
KONP Conditions Item
KONV Condition for Transaction Data
Handling Unit
VEKP Shipping Unit Header
VEPO Shipping Unit Item

Transportation

VTTK Shipment Header
VTTP Shipment Item
TVRO Routes
TVTK Shipment Types
VTRLK Delivery in shipment: Header

Sales Documents Copy Control Tables

TVAK Sales Document Types
TVCPA Sales Documents: Copying Control
T184 Sales Documents: Item Category Determination
TVASP Sales Documents: Blocking Reasons
TVCPF Billing: Copying Control
TVCPL Deliveries: Copying Control

Sales Documents Item Categories Copy Control Tables

TVAPT Sales document item categories: Texts
TVCPA Sales Documents: Copying Control
TVCPF Billing: Copying Control
TVCPL Deliveries: Copying Control
TVEPZ Sales Document: Schedule Line Category Determination
TVLP Deliveries: Item Categories
TVPT Sales documents: Item categories

Sales Documents Schedule Line Categories Copy Control Tables

TVCPA Sales Documents: Copying Control

Billing Documents Copy Control Tables

TVCPF Billing: Copying Control
TVFSP Billing: Blocking Reasons

Delivery Documents Copy Control Tables

T184L Sales Documents: Item Category Determination
TVCPF Billing: Copying Control
TVCPL Deliveries: Copying Control
TVLSP Delivery Blocks

SD Links to FI tables

KNVP Customer Master Partner Functions
KNVV Customer Master Sales Data
KNVD Customer master record sales request form
KNA1 General Data in Customer Master
KNB1 Customer Master (Company Code)
KNB5 Customer master (dunning data)

SD Links to MM tables

MARC Plant data for material
MVKE Sales data for material
MBEW Material Valuation
MARD Storage Location data for Material
T179 Materials: product hierarchy
MLAN Tax classification for material
MAKT material description
MARA General material data
MARM Units of measure of material
MTART – Material Types

SAP SD Structures

VBDKA - Document Header View for Inquiry, Quotation, Order
VBDPA - Document Item View for Inquiries, Quotation, Order
KOMK Communication Header for pricing
KOMP Communication Item for pricing

Steps to transport a Configuration Request

2011-05-24T16:06:00.000+05:30

1) You carry out config. changes in "Tata Group" client , (say100) in DEV server.

2) When you save, system prompts a Transport request dialogue, which is generally, saved by input of a description that identifies the Kind of Config carried out. User name appears by default with the Config request description when saved.

3) This is required to be tested in (Unit) Test Client say 120, by Client Copy of the Request using Tcode - SCC1.

4) On successful test results, we need to release the request (Tcode = SE01 or SE10). Here Collapse the request line once. Then click on Sub-task and press Transport button.. Then, Click on Main task and again press Transport button System gives success message.

5) Subsequently the BASIS Guy can transport the request to QUALITY and PRODUCTION Clients

SAP SD Interview Questions - BASIC KNOWLEDGE AND SYSTEM NAVIGATION

2011-05-24T16:04:00.001+05:30

1. Name two ways to start a transaction.
Dynamic Menu
Command Field

2. Why do you create user-specific parameters?
They supply defaults to R/3 fields. If a field is indicated, the system automatically fills in default value. Depending on the field definition, the entry can also be replaced with a value entered by the user. (Concept of PARAMETER ID)

3. Name the three different kinds of messages in the R/3 system. What is the difference
between them?
A message can have five different types. These message types have the following effects
during list processing:
A (=Abend):
The system displays a message of this message type in a dialog window. After the user
confirms the message using ENTER, the system terminates the entire transaction (for
example SE38).
E (=Error) or W (=Warning):
The system displays a message of this message type in the status line. After the user
chooses ENTER, the system acts as follows:
While creating the basic list, the system terminates the report.
While creating a secondary list, the system terminates the corresponding processing block
and keeps displaying the previous list level.
I (=Information):
The system displays a message of this message type in a dialog window. After the user
chooses ENTER , the system resumes processing at the current program position.
S (=Success):
The system displays a message of this message type on the output screen in the status
line of the currently created list.

4. What is a data dictionary or repository?
Central catalog that contains the descriptions of an organization's data and provides information about the relationships between the data and its use in programs and screens. The data descriptions in a Data Dictionary is also called metadata, i.e., data that describes other data. The ABAP/4 Dictionary stores system-wide data definitions. When you create a new data definition, the Dictionary tool does all the processing necessary to create the definition. You can use the Dictionary tool to look up the "definition" of objects in your R/3 System.

5. What is a matchcode?
Comparsion key. A matchcode allows you to locate the key of a particular database record (e.g. account number) by entering any field value contained in the record. The system then displays a list of records matching the specifications. If you want an end user to see a specific menu after logging on the R/3 system, how could
you do that? User maintenance transactions allow the system administrator to create and maintain user
master records. This includes the generation and assignment of authorizations and authorization profiles.

II CORPORATE STRUCTURE

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

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

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

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

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

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

5. Briefly explain the relationship between sales organizations and company codes.
Many to One.

6. What is the central organizational element in purchasing?
Purchasing Organization.

7. Explain the relationship between sales organizations and plants.
Many to Many.

8. Explain the relationship between sales organizations, plants and company codes.
Many to Many to One.

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

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

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

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

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

14. To what do you assign distribution channels and divisions?
Sales Organizations.

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

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

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

18. How many shipping points can you assign to a plant?
Many.

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

20. If you have a warehouse management system active, to what would you assign the
warehouse number?
Plant & Storage Location.

III MASTER DATA

1. Why does the customer master have different views?
In addition to the sales and distribution data, the accounting data is also important for a payer. Therefore one can create a customer master record centrally for the following partner functions:
:For the payer
:For the sold-to party who, in addition to the other partner functions, also takes on the
function of the payer.

2. Which different partner functions can a customer master record serve?
Customer:
o sold-to party
o ship-to party
o payer
o bill-to party
o One-time customer including all partner functions.

3. What is the structure of data in the customer master record?
Different data is maintained in each of the three areas:

General data, like address and telephone number, etc., is maintained for every customer. This data is only identified by the customer number, not by company code or sales area. Maintaining the data is possible from both the accounting view and the sales and distribution view.

Company code data is only of interest for the accounting department. It includes, for example, information on insurance or account management. This data applies to only one company code.

Sales and distribution data is only of interest for the sales and distribution department. It includes, for example, data on pricing or shipping. This data only applies to one sales area, and therefore is dependent on the sales structure (sales organization, distribution channel,division).

4. Would you have different customer numbers if your customer was serviced by more than
one company code?
No.

5. Would you have different customer numbers if your customer was serviced by more than
one sales organization?
No.

6. A material is produced in plant Boston, plant Dallas and in plant Chicago. How many
different material master number do you need?
Only one.

7. Is it possible to have different data for the same customer for different sales areas?
Yes.

8. Give examples of general data in the customer master record ?
Address, Control data, Marketing, Payment transactions, Contact person, Unloading points.

9. Give examples of general data in the material master record ?
This level contains the data applicable to all individual group companies, all plants, and all warehouses/stores belonging to an enterprise (corporate group). Examples of general data are details on a material's design (CAD drawings, for instance) and storage conditions (temperature range, whether the material is explosive or perishable, and so on).

10. Give examples of company -code-specific data in the customer master record?
This data is only of importance to the accounting department. It includes, for example, data on insurance and account management. Company code data only applies to one company code. If you edit the customer master record you must specify customer number and company code in order to access the screens containing company code data.

11. Which plant-specific data do you find in the material master record?
This level contains the data for each branch or plant location within a certain company. The data important to Purchasing is stored at this level. Examples of this data are the maximum and minimum order quantities of a material and the reorder level. You access the plant data by entering the plant key.

12. If a customer wishes to receive goods on Tuesdays only, how could you ensure that in the SAP R/3 system?
This can be done by specifying goods receiving hours - Time schedule of ship-to party which specifies the days and times that goods can be delivered.

13. Do you find any sales prices in the material master record?
Yes.

14. Name at least five different partner functions.
Examples of partner functions in Sales and Distribution: sold-to party, ship-to party, bill-to party, payer.
Examples of partner functions (roles) in Materials Management: ordering address, supplier of goods, invoicing party, different payee.

15. Which are the two partner functions in SD that have to be maintained in FI too ?
sold-to party, payer.

16. Can you assign a material to more than one division?
No.

17. If you want to create language specific sales texts for your material master, would you have
to create a new material master record?
No.

18. What is a material type and which material types do you know?
Raw materials, semi-finished products, finished products, trading goods, operating supplies.

19. Name the four standard industry sectors in SAP for the material master. For what do you
use them?
Branch of industry.
The industry sector groups together companies according to their activities (for example, plant engineering and construction, mechanical engineering, the chemical industry, and the pharmaceutical industry). Table-driven program support is provided via the industry sector: for example, for the selection of data fields on-screen, for the sequence of the screens, and for the allocation of a material to a material type.

20. For what or why do u use the classification system in sales? Give examples of objects u can classify in R/3.
For e.g., Variant Pricing of configurable products. Objects can be customers, products,
condition types.

21. Does storage-location specific data in the material master record apply for each plant?
This level contains the data specific to a storage location. Stock levels are an example of the data maintained for each storage location. You access the storage location data by entering the plant and storage location codes. This data structure facilitates the organization of material-related information within the entire enterprise. It prevents redundant storage of material data when the same material is used in more than one plant or stored at more than one storage location.
Example: Suppose the same metal casting is stored at two different locations. The design and purchasing data for this material would be identical. However, the data on the stock levels at each location would differ.

22. Name at least four views of the material master record.
Accounting : Valuation and costing information. Examples: standard price, past and future price, and current valuation.
Materials planning and control: Information for material requirements planning (MRP) and consumption-based planning/inventory control. Examples: safety stock level, planned delivery time, and reorder level for a material.
Purchasing: Data provided by Purchasing for a material. Examples: purchasing group responsible for a material, over- and underdelivery tolerances, and the order unit.
Engineering: Engineering and design data on a material. Examples: CAD drawings, basic dimensions, and design specifications.
Storage: Information relating to the storage/warehousing of a material. Examples: unit of issue, storage conditions, and packaging dimensions.
Forecasting: Information for predicting material requirements. Examples: how the material is procured, forecasting period, and past consumption/usage.
Sales and distribution: Information for sales orders and pricing. Examples: sales price, minimum order quantity, and the name of the sales department responsible for a certain material.

23. What are the possible units of measure for a material?
A material can be stored, transported and sold in various units of measure. In the SAP R/3 System, you can therefore define various units of measure which are maintained in the sales and distribution screens. However, you only need to maintain the fields of the units of measure if they deviate from the base unit of measure. If no other fields with units of measure are maintained, the system automatically takes the base unit of measure as a
basis for its calculations. You can enter the following units of measure in the sales and distribution screens:

Base unit of measure : Stocks of a material are managed in the base unit of measure. All quantity movements in other units of measure are converted automatically by the system into the base unit of measure.
Alternative unit of measure: If a product is managed in the base unit of measure "Piece" but is sold in the sales unit "Box", you must define the conversion factor. The alternative unit ofmeasure can define, for example, that 1 box of this material contains 12 pieces.

Sales unit : The unit of measure in which materials are sold is referred to as a sales unit (for example, piece or bottle). The value you define in the material master record is proposed during business transactions relevant for sales, such as the sales order. You can replace them with other alternative units of measure in the sales order.
Delivery Unit : The delivery unit refers to the unit in which materials can be delivered. Only exact multiples of the delivery unit can be delivered. For example, with a delivery unit of 30 bottles, 30, 60 or 90 bottles can be delivered, but not 100 bottles.
Quantity Specifications: Two different quantity specifications are used:
Minimum order quantity: The minimum order quantity refers to the minimum quantity the customer must order. A warning message appears if the minimum order quantity is not reached during order entry. The order can be entered in spite of the warning message.
Minimum delivery quantity : The minimum delivery quantity refers to the minimum quantity you must deliver to the customer. The minimum delivery quantity is automatically checked during delivery processing. A warning message appears during delivery processing if you enter a delivery quantity lower than the minimum delivery
quantity. The delivery can be created in spite of this warning message.

24. What is a Bill of material?
A bill of material is a complete, formally structured list of the components that make up a product or assembly. The list contains the object number of each component, together with the quantity and unit of measure. The components are known as BOM items. A bill of material can only refer to a quantity of at least 1 of an object.

25. Is the BOM used in the PP module only?
No. Also used in SD.

26. Explain what routing is?
Routing contains the operations required in production, and the production resources/tools, material components, and test equipment required to produce the product.

27. What is a work center?
A work center is an organizational unit where a work step is carried out, producing an output. The work center defines where and by whom an operation is to be carried out. A cost center is assigned to each work center in the work center master record. The work center has a particular available capacity. The activities performed at or by the work center are valuated by charge rates, which are determined by cost centers and activity types.
Work centers can be: Machines, People, Production lines, Groups of craftsmen .
IN Personnel Planning and Development (PD) work centers are the physical locations where tasks are carried out. A work center can represent anything as general as a geographic location, for example, the New York branch office. Or work centers can be very precisely defined. For example, a work center could represent a specific workstation, with
specific tools and equipment, on a specific floor, of a specific building.
IN Workflow Management a work center is a particular place which has been set up specifically so that employees can perform their duties within the corporate work system using working materials.

28. What does the account group of the customer /vendor control?
A collection of properties of accounts which determine the creation of master records. The account group determines the data that is relevant for the master record and a number range from which numbers are selected for the master records.Each master record must be assigned to an account group. Changes to the account group and the accompanying partner functions can only be made from a lower level to a higher level. For example, this means that a sold-to party cannot be assigned the function of a payer as fields which have already been maintained for this sold to party would have to be masked. However, you can assign the sold-to party function to a payer.
The account group ensures that for the different partner functions of a customer only the necessary screens and fields are displayed for input.

29. What are the two possible ways of control for the cost of a material in the material master
record?
Standard Price, Moving Average Price.

30. What is a valuation class?
Allocation of a material to a group of G/L accounts. Along with other factors, the valuation class determines the G/L accounts to be updated as a result of a valuation-relevant transaction (for example, a goods movement). Which valuation classes are valid depends on the material type. Several valuation classes can be valid for one material type. A valuation class can be valid for several material types.

31. A customer master record in SD is also an A/R(accounts receivables)in FI. When you create a customer master record you also have to specify the reconciliation account. For what is the reconciliation account used?
Account in G/L accounting, to which automatic entries are posted during a business activity. It is generally the case that several subledger accounts post to a common reconciliation account. This ensures that the developments in the subledger accounts are accurately reflected in the general ledger (i.e. in line with balance sheet conventions). You can set up a reconciliation account for, say, all overseas customers.

IV INTRODUCTION TO ORDER MANAGEMENT & SALES
1. Briefly describe the types and structure of the sales document and give examples of data that you find on the different levels.
Sales-related business transactions are recorded in the system as sales documents. There are, broadly speaking, four different groupings of sales documents:
1) Sales queries, such as inquiries and quotations
2) Sales orders
3) Outline agreements, such as contracts and scheduling agreements
4)Customer problems /complaints, such as free of charge deliveries and credit memo
requests.

Structure of the sales document and examples of data:
Header Data
The general data that is valid for the entire document is recorded in the document header.
This data includes the:
number of the sold-to party
number of the ship-to party and the payer
document currency and exchange rate
pricing elements for the entire document
delivery date and shipping point

Item Data
Whereas data in the document header applies to all items in the document, some data applies only to specific items. This data is stored at item level and includes the:
material number
target quantity for outline agreements
number of the ship-to party and the payer (an alternative ship-to party or payer can be
defined for a particular item)
plant and storage location specifications
pricing elements for the individual items

Schedule Line Data
An item consists of one or more schedule lines. The schedule line contains all the data that is needed for a delivery. For example, a customer orders 20 pieces of a material and you enter this as an item in the sales order. However, you can only deliver 10 pieces now and the remaining 10 pieces next month. In other words, you need to schedule two deliveries. The data for these deliveries (dates, confirmed quantities) are stored in two separate schedule lines. In sales documents where delivery data is not relevant -for example: contracts, credit and debit memo requests - the system does not create any schedule lines.
Data recorded in the schedule lines includes the:
schedule line quantity
delivery date
confirmed quantity

2. What is the difference between an inquiry and quotation ?
Inquiry: Request made to a vendor for a quotation for required materials or services. No availability check is done for inquiry.
Quotation: Offer from a vendor to a purchasing organization regarding the supply of materials or performance of services subject to predefined terms and conditions
A quotation consists of a number of items, in which the total quantity and delivery date of an offered material or service are specified.
The total quantity can be subdivided into several partial quantities with different delivery dates in the lines of a delivery schedule.

3. Do you always have to have a material master record number when you enter an item on a sales document (inquiry and quote)? If not what would you have to use to be able to enter information at item level?
No. Customer Material Information or Material Description.

4. If a customer doesn't place an order with you after you have sent him a quotation, what happens to the quotation document?
Remains active till the end of validity period.

5. Can you have alternative items in a sales order?
Yes.

6. If you reference an inquiry when creating a quotation, would the inquiry be updated?
Yes.

7. Can you copy one inquiry to many quotations?
No.

8. Can you copy several previous documents into one sales order?
Yes.

9. Do you always have to copy the entire quantities at item level when you reference a previous document?
No.

10. Can you make sure that business data in a sales order is only possible to maintain at header level?
Yes.

11. From where is the delivering plant transferred into the sales order?
Customer Master, Material Master.

12. Which partner function is relevant for the delivering plant? The sold-to-party , bill-to-party, payer, carrier or the ship- to- party?
Ship-to party.

13. Can you manually change the delivering plant in the sales order once it was defaulted from the master data?
Yes.

14. For what or why do you use the incompletion log?
To have a complete document so that it doesn’t affect subsequent processes.

15. Can u have different incompletion logs for diff item categories? Schedule line categories?
Yes.

16. If a document is incomplete can you still save the document?
Yes.

17. Which reference statuses can a document have at item level? which at header level?
Item level: Partial, Full.
Header level: Full.

18. What's the advantage of using text as a reference instead of duplicating it?
Can be modified if needed.

19. What three sources provide data for the creation of a sales document?
Material Master, Customer Master, Previous referenced documents.

20. Can you change addresses of partners manually in the sales document?
Yes.

21. Name several input tools that make order entry faster and give a definition of them?
Customer Material Information, Product Proposal , Referencing Documents.

22. In which business environment would you use only the single-line entry screen to create and save the order?
Telephone Sales, Simple Business.

23. If delivering plant not specified in the sales order, what could the system then not do?
Delivery Scheduling.

24. For what would you use the fast change function in sales entry?
Alternate Plants, Delivery or Billing Blocks

25. Name two ways to control that the customer can receive only certain materials?
Material Listing, Exclusion.

26. What does the item category control?
General Data
- Should pricing be carried out for the item?
- When should an item be regarded as completed? A quotation item, for example, can only be regarded as completed if the entire quantity has been copied into a sales order.
- Is it an item that refers to a material or is it a text item?
- Are schedule lines allowed for the item?
- May general business data, for example, the terms of payment at the item level, deviate from those at the header level?
- Should a system message appear if the item cannot be fully delivered?
- Which fields are relevant for the incompletion log?
- Which partner functions are allowed at the item level and which are mandatory?
- Which output (for example, an order confirmation) is allowed for the business transaction and which output determination procedure is used?

Shipping Data
- Is an item relevant for delivery?
o Should the weight and the volume of an item be determined?

Billing Data
- Is an item relevant for billing?
- Should the cost of the item be determined?
- Is it a statistical item? Pricing is carried out for statistical items. However, they are not added to the value of the order, that is, the customer is not charged for them.
- Should a billing block be set automatically for an item? For example, this may be important for items whose prices have to be clarified before billing.
* Is it a returns item?

27. Name the influencing factors for determining the item category in the sales document?
Sales Document type, Item Category Group, Higher Level Item, Item Usage.

28. Name the influencing factors for determining the scehdule line category in the sales document?
Item Category, MRP Type.

29. What does the sales document type control?
General Data
- Can the document be entered only with reference to a preceding document?
- Should the existing customer-material info record be taken into consideration?
- Should the delivery date be proposed?
- Must a customer number be entered when creating a document? For example, product
proposals can be entered without reference to a particular customer.
- Which order probability is defined?
- Should the division be taken from the material master record for every item or should an
alternative division specified in the header take precedence over the item specifications?
- How should the system respond if the division entered in the header deviates from the
division in the items?
- Should a credit limit check be made?
- From which number range should the document number for internal or external number
assignment come?
- Which fields are relevant for the incompletion log? The validity period, for example, is
important for contracts and must therefore be specified in the document.
- Can an incomplete document be saved or must all data be complete?
- Which partner functions are allowed and which ones are mandatory?

Shipping Data
- Which delivery type should the delivery resulting from the order have?
- Should delivery scheduling be carried out?
- Should transportation scheduling be carried out?
- Should a delivery block be set automatically for a specific reason? For example, a delivery
block may be appropriate for a free-of-charge delivery.
- You can define shipping conditions for a sales document type. These are copied into the
document regardless of what is defined in the customer master record.

Billing Data
Which billing type should the invoice resulting from the order or the delivery have?
Should a billing block be set automatically for a specific reason? For example, a billing
block may be appropriate if a credit memo request should first be checked before it is used
as the basis for a credit memo.

30. Can the sales document type be determined by the system?
No.

31. In R/3, can u automatically substitute 1 product for another? How? What would u have to create?
Yes. Product Selection / Material Determination.

32. Give a definition of replenishment lead time?
Total time for the in-house production or for the external procurement of a product. In inhouse
production the replenishment lead time is determined to cover all BOM levels.

33. What's the diff between checking availability with or w/o replenishment lead time (RLT)?
With RLT : Availability check is done only upto end of RLT. If material is not available the date on which RLT ends is displayed as Material Availability Date.
Without RLT : Availability check is unrestricted. Displays Delivery Dates as on which partial
deliveries can be made with available stock.

34. Name at least three item categories?
Standard Items : AFN, AGN, TAN.
Free of charge Items: AFNN, AGNN, TANN.
Non-stock Items : AFX, AGX, TAX.
Text Items : AFTX, AGTX, TATX.

35. Why would you use different item and schedule line categories?
Item categories are defined to provide additional control functions for the sales documents and thus meet the demands resulting from the different business transactions. The items in a sales document are divided into one or more schedule lines. These schedule lines differ from each other with respect to date and quantity. For some schedule lines, material requirements planning is not carried out; for other schedule lines, it is carried out. Also goods receipt, not goods issue, is posted for a schedule line defined in a returns document.

36. Can you change existing standard item categories?
Yes.

37. Can you create new sales order types?
Yes.

38. Different dates will be calculated in order entry scheduling . Can you name the lead time variables that will be taken into account?
Transportation lead time, Pick/pack time, Loading time, Transit time .

39. If you run out of stock in a specific plant can you check if there are quantities available in other plants?
Yes.

40. When u carry out availability check, which quantities or movements can the system takinto consideration?
The following elements can be included in the availability check:
Stocks : safety stock, stock in transfer, stock in quality inspection, blocked stock.
Inward and outward movements : purchase orders, purchase requisitions, planned orders,
production orders, reservations, dependent reservations, dependent requirements, sales
requirements, delivery requirements.

41. Give some examples of sales document types (description, not necessary the short code) that already set up in the standard system?
Indicator used to control the processing of the various sales documents which are defined in the system. E.g., OR, SO, BV, KR. Document types allow the system to process different kinds of business transactions, such as standard orders and credit memo requests, in different ways.

42. Can u maintain texts for a specific customer and store them in the system? If yes, where?
Yes. Customer Material Information.

43. When the system checks availability which scheduling would it use first?
Backward Scheduling.

44. Name the influencing factors for the determination of the availability date?
The following data is required for determining this date:
o Route from the shipping point to the ship-to party location
o Shipping point from which the goods are issued
o Loading group from the material master record
o Weight group determined from the order using the order quantity.

45. Name the three delivery possibilities when there is not enough stock available?
One Time Delivery, Complete Delivery, Partial Deliveries.

46. One example y u would have to create a text for a customer and copy it to the sales order?
Customer specific instructions.

47. What is the function of item category group?
The item category group determines how a material is processed in the sales order. It defines, for example, that pricing does not take place for a free of charge item, such as a business gift; or that inventory management is not carried out for a service. When processing sales and distribution documents, the system uses the item category group to determine the item category. The system determines the item category based on the item category group of the material and the current business transaction, and proposes it in the respective document. When creating the material types non-stock material and services, DIEN is proposed in both cases for the item category group, because the order processing for both material types is identical: for example, pricing is carried out for both, but no availability check.

48. On sales order, when the system confirms 20 pieces to be available at a certain date, would these 20 pieces still be available for other new sales order coming in later?
No.

49. What is a delivery group and why would you use it?
The complete delivery and delivery group functions enable you to combine some or all of the items in a sales order so that they are delivered to the customer together. The system determines automatically the latest delivery date possible for the delivery group and adjusts the schedule lines accordingly. Corresponding requirements for material requirements planning (MRP) are changed or re-determined.

50. What is backorder processing?
The backorder processing functions enable you to list relevant sales documents for specific materials and process them from the point of view of availability. You can assign available to promise (ATP) stock to outstanding order quantities. In addition, you can withdraw already confirmed quantities and reassign them to different items.
Backorder processing is only available for materials with individual requirements.

51. Can you link items in a sales order? If yes, when would you do that?
Yes. Promotional Items.

52. For what would you use BOM in sales? What two methods of BOM processing do you have in sales order entry? How can you control if the system should/should not explode a BOM in the sales order.
A bill of material (BOM) describes the different components that together create a product. A BOM for a bicycle, for example, consists of all the parts that make up the bicycle: the frame, the saddle, wheels, and so on. When you enter the material number of a bill of materials that is relevant for sales order processing, the system displays the material that describes the whole bill of materials as a main item. The components are displayed as subitems.
2 methods are:
o Processing by Main Item : ERLA & Processing by Sub-Item : LUMF
o BOM explosion can be prevented by specifying Item Category Group as NORM.

53. Credit limit checks is an example of a very close link between which two SAP modules?
SD & FI.

54. What are the two techniques in delivery scheduling?
Backward Scheduling & Forward Scheduling.

55. How does a third party deal work? Do you use a special sales order type for that? How could the system know that you want to process a third party deal?
By specifying item category as TAS using double-line entry in the sales order. No special order type is available.
By the item category group and/or material type in Material Master .

56. Name the several steps in consignment processing.?
Consignment fill-up, Consignment issue, Consignment pick-up, Consignment return.

57. Whats the difference between consignment pick-up and consignment return?
In consignment pick-up, customer returns consignment stock. When goods issue is posted, the relevant quantity is deducted from the customer's special stock and is added back to regular stock at the plant where the goods are returned. Total valuated stock remains the same since the returned stock was regarded as part of inventory even while it was at the customer's premises. This transaction is not relevant for billing. In consignment return, customer wishes to claim on consignment goods which have already been issued. When goods issue is posted, the relevant quantity is added to the customer's special stock at the plant where the goods are returned. Since the ownership of the goods is passed from the customer back to the company, the transaction is relevant for
billing. In this case, the customer receives a credit memo for the returned goods.

58. Can you control that an end user cannot copy a quote of customer A to a sales order for customer B? If yes, where?
Yes. By customizing Copying Control for header data.

59. Give some example for data that is copied from the customer (sold-to, payer, ship-to) to the sales order as well as for data that is copied from the material?
General data, payment terms, shipping details, delivery agreements, delivering plant.

60. What is returnable packaging processing?
Returnable packaging consists of materials that are stored at the customer location but which remain the property of the company. The customer is only required to pay for the returnable packaging if he does not return it by a specified time.

61. Name the two outline agreements in R/3 standard & explain the difference between them.
Agreements are arrangements between business partners regarding the granting of conditions over a specified time period. The agreement contains conditions which apply over a particular time period and which are settled together at the same points in time. An agreement can be settled once or periodically. The two outline agreements include Contracts and Scheduling Agreements.
Unlike a contract - which only contains an overall target quantity or value - a scheduling agreement also contains specific order quantities and delivery dates.

62. How many documents do you create when you release, deliver and invoice the first order from a contract?
Three : Sales order, Delivery note, Invoice.

63. What types of output can you have in sales?
Printer, Telex, Fax, Mail, EDI.

64. Can you automate output processing ? Do you always have to specify it manually?
yes. No.

65. Where would you specify which data should be copied (at header, item and schedule line level) when you copy from one document to another one?
Customizing Copy Control.

SHIPPING
1. Describe the flow of data from the sales order into the delivery for header and item and schedule line level data?
Header to* Header
Item to Header, Item.
Schedule line to Item.

2. Can you combine several sales orders into one delivery document ? If no, why not? If yes, would the system check certain criteria? What criteria?
No. When ship-to party or plant is different.
Yes. Availability of all items are confirmed.

3. Name the prerequisites that have 2 be fulfilled if u want 2 create a delivery for the order.

Header Level
There cannot be a delivery block at header level. The sales document must contain at least one item due for delivery before a delivery can be created for this document.

Item Level and Schedule Line Level
The schedule line must be due for shipping on the specified selection date. A schedule line becomes due for shipping as soon as the material availability date or the transportation scheduling date is reached. The schedule line cannot be blocked for delivery. The delivery quantity must be greater than one. The items in the order must be fully processed. If they are incomplete, u must first edit the incompleteness log in the order. You will find
information on the incompleteness log in the R/3 SD online documentation on sales.
The product status of the material must permit delivery.
For example, the product status for new products which have not been released for delivery does not allow them to be included in a delivery. Sufficient quantity of the material must be available.

4. If you create a delivery, would this automatically update the sales order?
Yes. The delivery status of the entire order results from the delivery status of the items. Until all items in the order have been fully delivered, the order has the status "Partially delivered". The entire document acquires the status of fully delivered once all the items have been fully delivered.

5. Name the different ways of creating deliveries.
Partial Deliveries, Complete Deliveries, Deliveries w/o reference, Grouped Deliveries.

6. How does the system determine the shipping point and the route in the sales order?
A shipping point can be determined for each order item. How the shipping point is determined depends on three factors:
**The shipping conditions from the customer master record (Shipping screen). A condition might be that the goods are to be delivered to the customer as soon as possible.
**The loading group from the material master record (Sales/Plant Data screen).You could, for example, specify a loading group that defines that the goods must always be loaded with a crane or a fork lift.
**The delivering plant. This plant is determined per order item either from the customer master record or from the material master record. However, you can also enter it manually for each order item.

7. Can you change the shipping point determined in the sales order manually?
Yes.

8. If u have several shipping points in a sales order at item level. What effect would that have on the delivery?
Each item will have individual deliveries.

9. Why would you carry out route determination in the delivery again?
To reconfirm the weight of the item.

10. At which different levels can you specify pick/pack and loading time?
Shipping point determination level : loading time.
Route determination level : pick/pack time.

11. Where do you specify the departure zone and the arrival zone for route determination?
Shipping point, Ship-to party.

12. How can the route influence the material availability date?
Transit time & Transportation lead time.

13. Why would you carry out availability check in the delivery?
The availability check is calculated using planned inward and outward movements of goods. Therefore the delivery situation might have changed in the meantime due to unforeseen circumstances, such as lost output. The availability check in the delivery takes any such changes into account.

14. Where u store partial/complete shipment agreements & over/under delivery tolerances?
Customer Master and Customer Material Information.

15. Explain the effects of printing out the picking list.
Updates the picking quantity in the delivery.

16. How does the syst automatically determine the picking storage location in the delivery?
Storage Condition.
Shipping Point.
Plant.

17. What is a transfer order and for what would you use it?
Document used to support every stock movement in the warehouse. It contains all the important movement data, such as the material to be transferred, the quantity to be transferred, the storage bins involved, and so on

18. Define a shipping unit?
Combination of materials which are packed together in a shipping material at a particular time. Shipping units contain items which in turn are made up of shipping units or delivery items.

19. What effects does goods issue have?
When the goods have left your plant, the business transaction is regarded as completed from the point of view of shipping. When goods are issued, the following functions take place in the system:

**The material stock is reduced by the goods issue quantity and the corresponding value changes take place in accounting. This ensures that the quantity and value flows are parallel.
**Material requirements for the delivery are reduced
**The delivery status is updated
**If you bill after goods issue, the delivery enters the billing work list

20. How can you delete a good issue?
You cannot cancel a goods issue posting in isolation. You are also unable to change goods issue quantities. If you make a mistake when processing a delivery, or if the goods are damaged leaving your plant and cannot be delivered, you must cancel the entire business transaction.
Procedure
After you have invoiced the delivery, for which the incorrect goods issue posting was
carried out, proceed as follows:
1. Enter a returns order (order type RE) for the customer and the material involved.
2. Create a returns delivery for the returns order. The system proposes the delivery
type. The delivery quantities in the returns delivery must correspond to the goods issue
quantities in the incorrect goods issue document.
3. Post "goods issue" for the returns delivery. The system automatically recognizes the
returns delivery as goods receipt and clears the original goods issue posting by carrying
out reverse posting.
4. Invoice the business transaction with a returns credit memo. The system proposes
billing type. The original billing document for the incorrect goods issue document is
cleared by this credit memo.

21. Is it possible to work without specifying a pick/pack or loading time for a shipping point?
Yes.

22. When do you initiate packing activity-before or after goods issue? What is the material type for shipping material?
Before goods issue. VERP.

23. When you post goods issue after packing, which two documents do you create?
Picking List, Invoice.

24. Can the delivery quantity and the picking quantity in the delivery docu be -different?
Yes.

PRICING

1. Could you explain what condition technique in SAP is?
Hierarchy of elements defining a data combination which leads to certain actions. In pricing the condition technique refers to the method by which the system determines prices from information stored in condition records. In Sales and Distribution, the various elements used in the condition technique are set up and controlled in Customizing. During sales order processing, the system uses the condition technique to determine a variety of important pricing information.

2. Name three areas/processes which use condition technique in SD?
Material determination, Output determination, Account determination.

3. What are the four basic elements of condition technique?
Condition Types, Condition Tables, Access Sequences, Pricing Procedures.

4. Please explain graphically the relationship between the four basic elements in condition techniques?
Procedures Ã* Condition Types Ã* Access Sequence Ã* Condition Tables Ã* Condition
Records.

5. Explain what a pricing procedure is?
The primary job of a pricing procedure is to define a group of condition types in a particular sequence. The pricing procedure also determines:
- Which sub-totals appear during pricing
- To what extent pricing can be influenced manually
- Which method the system uses to calculate percentage discounts and surcharges
- which requirements for a particular condition type must be fulfilled before the system
takes the condition into account.

6. Explain what a condition table and an access sequence is and the relationship between them?
**A condition table defines the combination of fields (the key) that identifies an individual condition record. A condition record is how the system stores the specific condition data that you enter in the system as condition records. For example, when you enter the price for a product or a special discount for a good customer, you create individual condition records.
**An access sequence is a search strategy that the system uses to find valid data for a particular condition type. It determines the sequence in which the system searches for data. The access sequence consists of one or more accesses. The sequence of the accesses establishes which condition records have priority over others. The accesses tell the system where to look first, second, and so on, until it finds a valid condition record. You specify an access sequence for each condition type for which you create condition records.

7.What is a condition type? What are the two main groups of condition types?
A condition type is a representation in the system of some aspect of your daily pricing activities. For example, you can define a different condition type for each kind of price, discount, or surcharge that occurs in your business transactions.
1) Fixed Amount & 2) Percentage.
Is SD the only module that uses condition technique?
No.

8. What is a condition supplement and why would you use it?
A condition supplement is a supplement for a particular condition type. For example, you can include a supplement every time you apply a material price. The supplement can contain various discounts. During pricing, the system automatically applies the discounts defined in the supplement every time it accesses a material price. You define for which condition types u want to use condition supplements in Customizing 4 Sales.

9. Which partner function is relevant when it comes to tax calculation in the sales order?
Ship-to party.

10. Name at least three different condition types in pricing?
Price, Discounts, Freight. PROO, K007, KF00.

11. U can create scales for prices and discounts. Name the four possible scale basis in R/3.
Value, Quantity, Gross & Net weight, Volume.

12. Where would you specify that a condition type is a discount or a surcharge?
In Condition Type Details Screen.

13. If somebody adds price elements manually in the sales order or changes a discount the
system determined automatically, do u have a possibility to see that in the sales order?
Yes.

14. You want to list all condition records for a certain material or a certain sales
organization. How would you do that?
By creating Pricing Reports.

15. Does the pricing procedure apply for the pricing data at item level or for the pricing data
at header level?
Both.

16. When u create a header condition manually in the sales order the system can copy the values in different ways 2 the items. Where would u specify how the system should process?
Condition Type.

17. Which data do you have to maintain in SD so that the system can determine the sales taxes in the sales order automatically?
Tax rate with or without Jurisdiction.

18. What does the condition exclusion indicator do for you?
The system can exclude conditions so that they are not taken into account during pricing in sales documents.

19. Can you explain what a statistical condition is? Give an example.
VPRS.

20. For what do you use customer hierarchies?
Pricing , Rebate.

21. Can you track cumulative values in R/3? If yes, it could be based on what?
Yes. Maximum Value, Maximum Orders, Maximum Quantity.

22. If u want to make sure that condition records apply for a certain time period only what would u have to do?
Validity Period to be specified in condition record.

23. What is a group condition?
Condition which can be used to determine a scale value based on more than one item in a document. The system groups the items using either the condition key for the appropriate condition record or a separately defined condition key.

24. Name influencing factors 4 pricing procedure determination during sales order entry?
Customer, Sales Document Type and Sales Area.

25. Can you copy condition records? If yes, are there any restrictions?
Yes. Field specific.

26. If you create a new condition type-do you also have to create a new condition table and a new access sequence?
Yes.

27. Where can you specify that a condition is mandatory?
In Pricing Procedure.

28. Tax jurisdiction processing is a close link between which two modules?
FI & SD.

29. Do you have to create a condition record for taxes in the SD application?
Yes.

BILLING

1. Name several billing types?
F1 : Order related Invoice F2 : Delivery related invoice.
F5 : Proforma Invoice for Sales Order F8 : Proforma Invoice for Delivery.

2. Can you delete an invoice?
No. You can cancel it and create cancellation document.

3. When you create an invoice in SD, how do you post it to FI?
Select Billing document Ã* Release To Accounting.
The system displays a message that the accounting document has been saved. If the billing document contains an error, the reason for not forwarding the document is displayed. If the release was successful, the posting status in the billing document is set to C (accounting document has been created). You find the posting status by selecting
Header Ã* Details in the billing document.

4. When you create an invoice can you carry out pricing again?
Yes.

5. From which documents can you create a proforma invoice?
Based on sales order or delivery.

6. Do you transfer a proforma invoice to FI ? If yes, how? If no, how do you customize the system in a way that the proforma invoice is not transferred to FI?
No. Billing status not assigned to proforma invoice. Posting bock in the billing document.

7. When you create a credit memo request do you always have to refer to a sales order or any other previous document?
Only sales order.

8. In R/3 how can u make sure invoices 4 a customer r always created on a specific date?
Billing Schedule.

9. Can you combine deliveries into one invoice? When would you do that?
Yes. If the header data and header partners for specified delivery or sales order are identical and if requirements for splitting do not apply.

10. Can you combine orders into one invoice?
Yes.

11. Can you split deliveries into several invoices? When would you do that?
Yes. If the data from the related reference documents differs in the header fields of the billing document. The system will automatically split the invoice.

12. For what do you use the billing due list? What previous step in the process is necessary that a delivery appears in the billing due list?
Selection criteria - sold-to party, billing date or receiving partner.
a) separate invoice for each delivery
b) split one sales order for delivery into several invoices.
c) combine several sales orders for delivery into one invoice.

13. Name the five possible influencing factors for account determination for invoices?
Chart of accounts of the company code
Sales organization
Account assignment group of the customer (from the customer master record, Billing
screen, Account group field)
Account assignment group of the material (from the material master record, Sales 2
screen, Account assignment group field)
Account key (from the pricing procedure)

14. Can one business area be valid for several company codes?
Yes.

15. What are the two possible ways to transfer sales data to business areas? Where do you specify which way you want to use?
sales area (if the accounts are to be posted according to sales)
plant/division (if the accounts are to be posted according to products)

16. There is an interface between SD and FI in invoicing. State another interface b/w them?
Credit check, Tax calculation, Cost estimate.

17. What is rebate processing?
A rebate is a special discount which is paid retroactively to a customer. This discount is based on the customer's sales volume over a specified time period

18. What is an invoice list? Which prerequisite are necessary to use an invoice list? How does an invoice list differ from a collective invoice?
Invoice lists let you create, at specified time intervals or on specific dates, a list of billing documents (invoices, credit and debit memos) to send to a particular payer.
The billing documents in the invoice list can be single or collective documents (collective invoices combine items from more than one delivery).
The standard version of the SAP R/3 System includes two types of invoice lists:
- for invoices and debit memos
- for credit memos
If you wish, you can process invoices, debit memos, and credit memos at the same time. The system automatically creates a separate invoice list for credit memos.

Prerequisites for Invoice Lists
- Condition type RL00 (factoring discount) must be maintained and, if required, condition type MW15 (VAT: factoring discount tax)
- An invoice list type must be assigned to each billing type that you want to process - two invoice list types: LR for invoices and debit memos, LG for credit memos
- Copying requirements must be defined (for example, the payer, terms of payment, and other fields that must be identical in the documents to be included in the invoice list)
In addition, before u process an invoice list, u must maintain the following master data:
- A customer calendar must be defined, specifying the time intervals or dates on which invoice lists are to be processed
- The customer calendar must be entered in the Billing view of the customer master record of the payer (field: Inv. list sched.)
- Pricing condition records for the condition type RL00 and, if necessary, MW15
Output condition records 4 condition types LR00 (invoice list) and RD01 (single invoice)

Collective Invoice
If the header data and the header partners for the specified deliveries or sales orders are identical and if the requirements for splitting do not apply, one billing document is created for all the deliveries or sales orders.

19. What is a product hierarchy and for what can it be used?
Alphanumeric character string for grouping materials by combining various characteristics. The product hierarchy is used for evaluation and pricing purposes.
In Product Cost Controlling (CO-PC) : Structure consisting of the plant, product group, product, and order. Used for the interactive analysis of the product costs for each level of the hierarchy.

20. Can you name the two types of billing plans in the standard R/3 system?
Periodic billing, Milestone billing.

21. Can you partially settle rebate accruals?
Yes.

22. For what would you use a lump sum payment?
A lump sum payment is a special condition which does not depend on sales volume but on a promotional performance such as a front of store display or a local advertisement.

CUSTOMISING
1. Explain what the IMG 'Implementation Guide is?
Tool for configuring the SAP System to meet customer requirements.

2. Explain how you can use the R/3 project Management in an implementation?
For each business application, the implementation guide explains all the steps in the implementation process & tells you the SAP standard (factory) settings & describes system configuration work (activities) and opens the activities interactively. Implementation guides are structured as hypertext. The hierarchical structure reflects the structure of the R/3 business application components, and lists all the documentation to do with implementing the R/3 System.

3. Once you have activated the company IMG can you still add modules/areas?
Yes.

4. If you deactivate the module CO in the company IMG could you still select the CO module in a project you create?
No.

5. Is it possible to link R/3 projects to the MS project?
Yes.

6. What is the procedure model and how can it be used in an implementation?
The R/3 Procedure Model is both the methodological framework for the implementation and upgrade processes and a powerful tool that supports you at every stage of the implementation process. The R/3 Procedure Model provides all the fundamental understanding you need at the cross-application level for implementing R/3 application components successfully, a hierarchically-structured plan of the activities, a correct sequence of the activities & the link to the system setting activities

7. Explain shortly what the SAP business Navigator is and how it can be used in an implementation.
The Reference Model integrated into the R/3 System. The various ways into Business Navigator (the views) help you call just the models and list displays you need in the R/3 Reference Model. You can access other R/3 System components directly from the models, for example: data models, transactions, documentation.

8. What two ways of number assignment for documents or master data do you know? Explain the difference between them.
Internal & External.

9. Can you share master data between several sales areas?
Yes.

10. What does the account group of the customer control?
Number assignment, Screen Layout.

11. What r the 2 influence factors 4 field selection 4 customer master record maintenance?
Account Group, Transactions.

12. Name at least five features that you can control for the sale document type?
Text, Partner, Pricing, Taxes, Output, Delivery.

13. Give an example of when you would specify that a sales document can only be created referencing another sales document?
Returns can only be created referencing sales order.

14. Why do you have different sales document types in R/3?
For business transactions.

15. Name at least three features controlled by the sales document type?
Pricing, Taxes , Delivery.

16. Name at least five features that you can control for the item category?
Pricing, Relevance for delivery, Relevance for billing, Incompletion log, Partner, Tax.

17. Name at least five features that you can control for the schedule line category?
Relevance for delivery, Availability check, Transfer of Requirements, Goods Movement, Purchasing and Incompletion log.

18. Explain how the system automatically determines the item category in the sales order.
Sales document type + Higher level Item category + Item category group + Item Usage.

19. Explain how system automatically determines schedule line category in the sales order?
Item category + MRP type.

20. Once the system determined the item level schedule line category automatically in the sales order, can you still change it manually?
Yes.

21. At which levels in the sales document can you have different incompletion procedures?
Sales Document Type, Item Category, Schedule Line Category, Partner Functions, Sales Activities.

22. What is the item category group? Where do you maintain it?
The item category group determines how a material is processed in the sales order. It defines, for example, that pricing does not take place for a free of charge item, such as a business gift; or that inventory management is not carried out for a service. When processing sales and distribution documents, the system uses the item category group to determine the item category. The system determines the item category based on the item category group of the material and the current business transaction, and proposes it in the respective document.
When creating the material types non-stock material and services, DIEN is proposed in both cases for the item category group, because the order processing for both material types is identical: for example, pricing is carried out for both, but no availability check. It is maintained in the material master.

23. What do you control at item category level in the delivery?
Relevance for Picking, Determination of Picking Location, Minimum Delivery Quantity.

24. Do you have schedule lines in the delivery?
No.

25. Item categories from the sales order are copied into the delivery. What happens if you
add a new item in the delivery? can the system still automatically determine the item
category for the delivery? If, yes, what do you have to do?
You can only enter an item that is not dependent on an order in a delivery if the delivery permits the item category for that item. The item category is determined on the basis of the delivery type and item category group in the material master record. Thus, items for which an order has to be created first cannot be added to a delivery. Which materials can be included in a delivery, depend on your system configuration. In the standard
version of the SAP R/3 System, only materials with the item category VERP can be added to a delivery.

26. What does the billing type control?
The document number
The partner functions allowed at header level
The partner functions allowed at item level
The billing type that can be used to cancel the billing document
The transfer status of the billing document:
**Transferred to financial accounting
**blocked from transfer
**not transferred
The procedure for account assignment in Financial Accounting
The allowed output for a business transaction and the procedure for output.

27. When you think of the document flow, what do you control for it in customizing?
You can specify for a particular sales document type, which document type is to be assigned to copied reference documents, and which item categories or schedule line categories are to be copied. You must also make specifications for copying requirements and data transfer, as well as quantity and value updates in document flow. This must be done for each copying procedure at header, item and, if necessary, schedule line level on a detail screen. You can specify partner procedures for the customer master (linked to the account
group) and you can specify partner procedures for the sales document.

28. Can you have different partner procedure at sales document type and item category
level? If yes, why would you want to have different procedures for the item category?
Yes. Different Ship-to party.

29. What is a partner type? Give some example?
The partner type is an indicator which informs you of the type of partner, for example, partner type customer "KU".

30. U want to set up a new condition type. Name the necessary steps u have to do if u want the system to determine the new condition type automatically during sales order entry?
Check to what extent you can use the condition types contained in the std SAP R/3 Sys.
Create new condition types by copying a similar conditions type and changing it according to your requirements. One reason for creating a new condition type is u may require a calculation rule for a discount which is not available in the standard system.
Specify an alphanumeric key which can have up to 4 digits, and a textual description.
Specify an access sequence for the condition types. You do not need to specify an access sequence for header conditions.
Maintain the detail screen of the condition type.
You can also assign a reference condition type if the condition types you are working with are similar. Then you will only have to maintain condition records for the reference condition type.
In addition, you can define the upper and lower limits for the value of a condition at condition type level. This way, you limit the amounts or the scale values in the corresponding condition records.

31. When you think of the five possible elements necessary for the account determining during posting of a sales invoice where from does the system get the information?
Chart of Accounts, Sales Organization, Payer, Material Master, Account Key.

32. Name the necessary steps to setup a route?
Define the transportation connection points which mark the beginning and end of a leg
Define the leg by specifying the transportation connection points at the beginning and end
Define the modes of transport and shipping types which are dependent upon the mode of transport.
Define the routes by listing the individual legs one after another. The sequence of legs constituting the route determines the itinerary. When you string together the individual legs of the route, you must also specify the shipping type for each leg.
As a simple alternative you can also define routes without specifying them more precisely by defining legs. Note that in this case the system cannot propose the office of exit for export.

33. During route determination the system also needs to know the departure Zone of the goods to be shipped. How does this information come into the sales order?
Customer Master.

34. What is the scope of check during availability check and what do you specify with it?
Stocks:
Safety stock, stock in transfer, stock in quality inspection, blocked stock.
Inward and outward movements:
purchase orders, purchase requisitions, planned orders, production orders, reservations, dependent reservations, dependent requirements, sales requirements,
delivery requirements.

35. Where do you assign text determination procedures for customer master records and for documents?
Account Group, Item Category.

36. Can you make texts mandatory for a customer master or a sales document?
Yes.

37. Give examples for standard output types in SD.
Order Confirmation, Delivery Note , Invoice.

38. Can you specify when output should be created? If yes, what possibilities do you have?
Yes. Print out, Mail, EDI, Fax.

39. What does the material type control?
The material type determines a material's procurement type. It also controls
- screen sequence
- field selection
- number assignment type in material master maintenance
- inventory management type
- account determination

A Short Tutorial on User Exits

2011-05-24T14:29:00.000+05:30

User exits :

1. Introduction
2. How to find user exits
3. Using Project management of SAP Enhancements

1. Introduction:

User exits (Function module exits) are exits developed by SAP. The exit is implementerd as a call to a functionmodule. The code for the function module is writeen by the developer. You are not writing the code directly in the function module, but in the include that is implemented in the function module.

The naming standard of function modules for functionmodule exits is:
EXIT_<3 digit suffix>

The call to a functionmodule exit is implemented as:
CALL CUSTOMER.-FUNCTION <3 digit suffix>

Example:

The program for transaction VA01 Create salesorder is SAPMV45A

If you search for CALL CUSTOMER-FUNCTION i program
SAPMV45A you will find ( Among other user exits):

CALL CUSTOMER-FUNCTION '003'
exporting
xvbak = vbak
xvbuk = vbuk
xkomk = tkomk
importing
lvf_subrc = lvf_subrc
tables
xvbfa = xvbfa
xvbap = xvbap
xvbup = xvbup.

The exit calls function module EXIT_SAPMV45A_003

2. How to find user exits?

Display the program where you are searching for and exit and search for CALL CUSTOMER-EXIT

If you know the Exit name, go to transaction CMOD.

Choose menu Utillities->SAP Enhancements. Enter the exit name and press enter.

You will now come to a screen that shows the function module exits for the exit.

3. Using Project management of SAP Enhancements, we want to create a project to enahance trasnaction VA01 .

- Go to transaction CMOD
- Create a project called ZVA01
- Choose the Enhancement assign radio button and press the Change button

In the first column enter V45A0002 Predefine sold-to party in sales document.

Note that an enhancement can only be used in 1 project. If the enhancement is already in use, and error message will be displayed

Press Save

Press Components. You can now see that enhancement uses user exit EXIT_SAPMV45A_002. Double click on the exit.

Now the function module is displayed. Double click on include ZXVVAU04 in the function module

Insert the following code into the include: E_KUNNR = '2155'.

Activate the include program. Go back to CMOD and activate the project.

Goto transaction VA01 and craete a salesorder.

Note that Sold-to-party now automatically is "2155"

Down Payment Processing : Configuration Steps

2011-05-23T13:17:00.001+05:30

The following Customizing settings have to be made for down payment processing:

Settings for the billing plan - To activate the billing plan function, maintain the materials, for which you wish to process down payments, with item category group 0005 (milestone billing). This gives the item type TAO via item type determination. The item type TAO calls up the billing plan function.

You need to implement the following activities in the billing plan for down payments:

Maintain deadline category - This determines the billing rule (percentage or value down payment) for the down payment request. The system assigns billing type FAZ (payment request) defined in the standard system with billing category P. (For the billing type FAZ there is the cancellation billing document type FAS in the standard system).

Maintain the deadline proposal - Use the down payments that are due for the proposed deadlines.

Maintaining a Pricing Procedure with the Condition Type AZWR:

In the standard system the condition type AZWR is delivered for the down payment value already provided but which has not yet been calculated. You must include this condition type in the relevant pricing procedure before output tax. Enter condition 2 (item with pricing) and the calculation formula 48 (down payment clearing value must not be bigger than the item value) for the condition type AZWR. Before the condition AZWR you can create a subtotal with the base value calculation formula 2 (net value). If the condition AZWR is changed manually, you can get information on the original system proposal from the subtotal.

Maintain the printing indicator - The pricing procedure cannot be marked as a transaction-specific pricing procedure (field Spec.proc.) The condition type

AZWR has the calculation type B (fixed amount) and the condition category E (down payment request / clearing).

Maintaining the Billing Document - In the standard system there is the billing type FAZ (down payment request) and the billing type FAS for canceling . The down payment is controlled using the billing category P of the billing type. A billing type becomes a down payment request when the billing category P is assigned. You have to maintain blocking reason 02 (complete confirmation missing) for the billing documents and assign it to billing type FAZ.

Copying control - Copying requirement 20 must be entered in copying control at item level for the down payment request. In the standard system the order type TA for copying control is set up according to the billing type FAZ for the item category TAO. Copying requirement 23 must be entered in copying control at item level for down payment clearing.

In the standard system the order type TA for copying control is set up according to the billing type F2 for the item category TAO.

Financial Accounting settings - A prerequisite for down payment processing is that the account is assigned to the underlying sales document. To do this, change the field status settings in Customizing as follows:

Set reconciliation accounts (transaction OBXR) - For the `received down payments' and `down payment requests' from the G/L accounts you have selected, you should assign the field status definition G031.

Maintain accounting configuration (transaction OBXB) - For the down payments (posting key ANZ in the standard system) and the output tax clearing (posting key MVA in the standard system), you must maintain the posting key. You must also carry out a G/L account number assignment for the tax account.

Maintain the posting key (transaction OB41) - For posting key 19, set the sales order as an optional field

Maintain the field status definition (transaction OB14) - For field status variant 0001, field status group G031, set the sales order as an optional field

Assign the company code to the field status variants (transaction OBC5)

Standard SAP SD Reports

2011-05-18T10:51:00.001+05:30

Sales summary – VC/2

Display Customer Hierarchy – VDH2
Display Condition record report – V/I6
Pricing Report – V/LD
Create Net Price List – V_NL
List customer material info – VD59
List of sales order – VA05
List of Billing documents – VF05
Inquiries list – VA15
Quotation List – VA25
Incomplete Sales orders – V.02
Backorders – V.15
Outbound Delivery Monitor – VL06o
Incomplete delivery – V_UC
Customer Returns-Analysis – MC+A
Customer Analysis- Sales – MC+E
Customer Analysis- Cr. Memo – MC+I
Deliveries-Due list – VL04
Billing due list – VF04
Incomplete Billing documents – MCV9
Customer Analysis-Basic List – MCTA
Material Analysis(SIS) – MCTC
Sales org analysis – MCTE
Sales org analysis-Invoiced sales – MC+2
Material Analysis-Incoming orders – MC(E
General- List of Outbound deliveries – VL06f
Material Returns-Analysis – MC+M
Material Analysis- Invoiced Sales – MC+Q
Variant configuration Analysis – MC(B
Sales org analysis-Incoming orders – MC(I
Sales org analysis-Returns – MC+Y
Sales office Analysis- Invoiced Sales – MC-E
Sales office Analysis- Returns – MC-A
Shipping point Analysis – MC(U
Shipping point Analysis-Returns – MC-O
Blocked orders – V.14
Order Within time period – SD01
Duplicate Sales orders in period – SDD1
Display Delivery Changes – VL22

IDoc T-Codes

2011-05-18T10:50:00.001+05:30

SALE – IMG ALE Configuration root
WE20 – Manually maintain partner profiles
BD64 – Maintain customer distribution model
BD71 – Distribute customer distribution model
SM59 – Create RFC Destinations
BDM5 – Consistency check (Transaction scenarios)
BD82 – Generate Partner Profiles
BD61 – Activate Change Pointers – Globally
BD50 – Activate Change Pointer for Msg Type
BD52 – Activate change pointer per change.doc object
BD59 – Allocation object type -> IDOC type
BD56 – Maintain IDOC Segment Filters
BD53 – Reduction of Message Types
BD21 – Select Change Pointer
BD87 – Status Monitor for ALE Messages
BDM5 – Consistency check (Transaction scenarios)
BD62 – Define rules
BD79 – Maintain rules
BD55 – Defining settings for IDoc conversion

WEDI – ALE IDoc Administration
WE21 – Ports in Idoc processing
WE60 – IDoc documentation
SARA – IDoc archiving (Object type IDOC)
WE47 – IDoc status maintenance
WE07 – IDoc statistics

BALE – ALE Distribution Administration
WE05 – IDoc overview
BD87 – Inbound IDoc reprocessing
BD88 – Outbound IDoc reprocessing
BDM2 – IDoc Trace
BDM7 – IDoc Audit Analysis
BD21 – Create IDocs from change pointers
SM58 – Schedule RFC Failures

Basic config for Distributed data:
BD64: Maintain a Distributed Model
BD82: Generate Partner Profile
BD64: Distribute the distribution Model

Programs:

RBDMIDOC – Creating IDoc Type from Change Pointers
RSEOUT00 – Process all selected IDocs (EDI)
RBDAPP01 – Inbound Processing of IDocs Ready for Transfer
RSARFCEX – Execute Calls Not Yet Executed
RBDMOIND – Status Conversion with Successful tRFC Execution
RBDMANIN – Start error handling for non-posted IDocs
RBDSTATE – Send Audit Confirmations
For testing you can use WE19

Third Party Order Processing

2011-05-16T11:05:00.001+05:30

Third party order processing is as follows:

Assume three companies X, Y and Z
X – The company,
y – The customer
Z – Vendor

When ever X gets a PO from Y to supply some goods, X has an option of either manufacturing those goods or procuring those goods.

If he is procuring the goods, there are two methods that are generally followed:

Method 1) After receiving the PO from Y, X creates a sales order against Y.
Now at the same time he also creates a PO to a vendor Z to produce the goods
Z produces the goods and supplies to X
X receives the goods from Z
Then X delivers the same goods to Y.
After that X invoices Y and Z invoices X.

Note : Here there is no direct/ Indirect relation between Z and Y.

This process is known as Trading Process. and the Material here is created with Material type HAWA.

The other method is a Third party order processing method:

Here the glaring difference is that instead of Z supplying the material to X and X in turn supplying the same material to Y.

X authorizes Z to supply the material to Y on his behalf and notify him once the delivery is complete.

Now Z supplies the material to Y and acknowledges the same to X.

Z will send a copy of delivery acknowledgement and invoice to X.

After receiving the delivery confirmation and invoice from Z, X has to verify the invoice and this process is known as invoice verification and is done in SAP through Tcode MIRO.

The next step for X is to create an invoice and submit to Y

Only after the invoice verification document is posted then only X can create an invoice for Y.

This is the business flow that is followed for third party order configuration.

There are few steps that have to be configured to enable the system to function as mentioned above.

Step1)
If you are always followwing a third party process for a material then you have to create the material using item category group BANS.

The procument type should be marked as External procurement (F) in MRP 2 view of the material master record.

if you are not always allowing third party order processing then u can create a material master record with item category group as NORM and the procurement type should be marked as ( X) meaning both types of procurment ( in house manufacturing and external procurement).

step 2)
the item category in the order should be manually changed as TAS.
For that you need to confugure the item category determination

ord type + item cat grp + usge + Hiv level = Item cat + Manual item cat

OR + NORM + + = TAN . + TAS
OR + BANS + + = TAS

Step 3)
make sure that during the item category configuration for TAS you need to mark relevnat for billing indicator as F

step 4)
The schedule line cateogry for this type should be CS.
make sure that you mark subsequent type as NB – purchase requisition in this schedule line category as this will trigger the purchase requision order immediately after the creation of the sales order and the PO to vendor is created against this purchase requiesion.