Tuesday, September 18, 2007

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

There are two ways to do this:

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

Tuesday, September 11, 2007

SAP SD Transaction Codes

I found a way to get hidden customizing Tcodes.

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

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

SAP SD Tables

Table Description


Customers KNA1 General Data
KNB1 Customer Master – Co. Code Data (payment method, reconciliation acct)
KNB4 Customer Payment History
KNB5 Customer Master – Dunning info
KNBK Customer Master Bank Data
KNKA Customer Master Credit Mgmt.
KNKK Customer Master Credit Control Area Data (credit limits)
KNVV Sales Area Data (terms, order probability)
KNVI Customer Master Tax Indicator
KNVP Partner Function key
KNVD Output type
KNVS Customer Master Ship Data
KLPA Customer/Vendor Link

Sales Documents VBAKUK VBAK + VBUK
VBUK Header Status and Administrative Data
VBAK Sales Document - Header Data
VBKD Sales Document - Business Data
VBUP Item Status
VBAP Sales Document - Item Data
VBPA Partners
VBFA Document Flow
VBEP Sales Document Schedule Line
VBBE Sales Requirements: Individual Records

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

Billing Document VBRK Billing Document Header
VBRP Billing Document Item

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

Suppressing Fields in Sales Order

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

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

User exits in the program MV45AFZZ-USEREXIT_FIELD_MODIFICATION

This user exit can be used to modify the attributes of the screen fields. To do this, the screen fields are allocated to so-called modification groups 1 - 4 and can be edited together during a modification in ABAP.

If a field has no field name, it cannot be allocated to a group. The usage of the field groups (modification group 1-4) is as follows:

Modification group 1: Automatic modification with transaction MFAW

Modification group 2: It contains ‘LOO’ for step loop fields

Modification group 3: For modifications which depend on check tables or on other fixed information

Modification group 4: is not used
The FORM routine is called up for every field of a screen. If you require changes to be made, you must make them in this user exit. This FORM routine is called up by the module FELDAUSWAHL.

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

Below is the sample code

IF SCREEN-NAME = ‘VBKD-ABSSC’.

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

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

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

User Exit for customizing your own error message for PGI failure

USEREXIT_SAVE_DOCUMENT_PREPARE

Find User Exit

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

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

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

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

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

Please note the following points :

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

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

Monday, September 10, 2007

SD - Q and A

Org Structure

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

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

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

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

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

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

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

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

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

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

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

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

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

The business area is defined in Customizing for Sales.

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

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

Briefly explain the relationship between sales organizations and company codes.

Many to One.

What is the central organizational element in purchasing?

Purchasing Organization.

Explain the relationship between sales organizations and plants.

Many to Many.

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

Many to Many to One.

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

Yes in CO .

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

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

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

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

Give a definition of plant (in SAP).

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

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

Classification: Business object

Structure: A plant can assume a variety of roles:

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

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

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

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

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

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

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

Yes.

To what do you assign distribution channels and divisions?

Sales Organizations.

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

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

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

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

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

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

Yes.

How many shipping points can you assign to a plant?

Many.

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

None.

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

Plant & Storage Location.

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

Pricing

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

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

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

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

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

Disallowing Condition Types - How I can accomplish the following:

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

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

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

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

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

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

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

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

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

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

Rebate Agreement

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

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

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

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

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

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

Customer Master

How to create the customer master?

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

XD01 Create Customer (Centrally)
XD02 Change Customer (Centrally)
XD03 Display Customer (Centrally)
XD04 Customer Changes (Centrally)
XD05 Block customer (centrally)
XD06 Mark customer for deletion (centr.)
XD07 Change Customer Account Group
XD99 Customer master mass maintenance
XDN1 Maintain Number Ranges (Customer)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

The pricing procedure will reject the conditions in the sales order

3. Do header condition type have an access sequence?

No

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

Company - sales org - credit control area

What are sales area and its components?

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

5. What are legacy systems?

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

6. What is cut over strategy?

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

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

7. What are Cumulative Condition Records?

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

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

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

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

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

10. What is meant by delivery group?

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

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

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

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

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

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

13. What is z transaction?

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

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

Yes.

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

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

16. What makes the immediate delivery in cash sales?

Order type immediate delivery switch on.

Friday, September 7, 2007

Set Material Master Price of a material as sales price

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

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

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

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

This is how it goes :-

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

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

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

The pricing procedure than looks like that:

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

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

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

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

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

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

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

Alternative Calculation Type:

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

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

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

Alternative Condition Base value :

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

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

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

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

Consignment Process

Scenario -

1. Client creates a consignment order for their distributor.

2. The consignment stock sits at the distributor location. The distributor sells some of this stock to end customer.

3. Client creates an issue order for this quantity, this order has end customer as the ship to as well as bill to parties.

4. When the goods are delivered against this order, the consignment stock is reduced.

5. Client then creates an invoice for the end customer.

SAP Solution -

1. Create Cosignment fill up order of type KB with distributor as sold-to, ship-to and bill-to and payer.

2. Create delivery for this order and do PGI, which shifts this stock to ‘customer consignment stock” (special stock w).

3. Assumption - the master data for the end customer exists in the system and has all mandatory partner functions defined.

4. Create a consignment issue order of type KE, which has sold-to as the distributor and ship-to, bill-to as the end customer.

5. Create delivery and do the PGI, which reduces the consignment stock.

6. Create invoice, which has the end customer as bill-to and the distributor as ‘payer’.