Availability Check:
It determines if the desired delivery quantity can be met on requested delivery date.
ATP : it is the stock quantity which are not reserved and can be delivered to customer.
ATP = present stock + planned inward – planned outward.
Types of Availability check:
- Check against ATP quantity
- Check against Product allocation
- Check against planning
Different dates:
Order date : Date of order
Material available date: date on which material available for picking and packing
Transportation planning date: date from which transportation planning started
Loading date: date on which material is loaded in vehicle.
Goods issue date: date on which material is dispatched from the plant.
Delivery date: date on which customer receives the Goods at his premises.
Different Time:
Transit time – from goods issue to delivery date
Loading time – Loading date to goods issue date
Lead time for transportation planning – trans. Planning date to loading date
Pick/Pack time - from material available to loading date
During availability check system calculates all this time and dates into consideration.
First we assume that we are doing availability check without RLT.
Case – 1 confirmation on required delivery date. Here the main date is material availability date. How it is calculated? System first takes into account the requested delivery date than it searches for transit time and based on it, system determined goods issue date. From goods issue date it deducts loading time and accordingly it determines Loading date. After that it searches for Pick/Pack time and deduct it from the Loading date and it determine the Material availability Date.
Now the system will calculate whether the required quantity will be available or not. This it calculates from today’s stock + planned inward – planned outward.
Case – 2 Confirmation at a later date.
In the above first case system carried backward scheduling, but suppose the material is not available on the mentioned material availability date, then the system carryout Forward scheduling. Here system will first determine on which date the material will be available and accordingly it will determines other dates.
Case –3 Partial delivery
If it is allowed in customer master, than system will carryout partial deliveries based on material availability.
Availability Check with RLT:
RLT – Replenishment Lead time. It is the time required to produce or procure the material. Now suppose if we do availability check with RLT, than even material is not available on the availability date but the availability date is after the RLT, than the system will confirm the quantity. It will assume that we can produce or procure the materials per the RLT.
For delivery, delivery item category can be used to control whether an availability check takes place in delivery.
Configuration:
In MM
- Define MRP controllers and assign it in Material master
- Defines Floats(Schedule margin key) and assign it in material master.
In SD-BF for availability check with ATP logic
- Define checking Group
-
- Define material block for other user. You can block other user to use this material while you are doing availability check. This is defined for checking group.
- Define checking group default value. Mat type + Plant = checking group FERT + C000 = 01
- Carryout control for availability check.
Define controls for checking group(availability check) + checking Rule(Predefined)
Like 01 Daily Req. + A SD Order or B SD Delivery.
Based on this combination you will define which stocks you will consider, which inward/outward movement you will consider and RLT time will be considered or not for determining material availability date.
- Define Procedure for Requirement class. Activate TOR and Avail. Check at Req. class level.
- Define procedure for each schedule line. Activate TOR and Avail. Check at sch. Line level.
- Determine procedure for each delivery item. Activate avail. Check for deli. item
- Checking rule for updating backorders. Plant + checking rule C000 + A
- Define default setting. Here you define for each sales area whether the system should pop up a window whenever there is a shortfall of material. The window will show the dates on which the material will be available. It will give option like Accept the Proposal, Onetime delivery, complete delivery.
Saturday, January 30, 2010
BF-Transfer of Requirement
Transfer of Requirement:
Transfer of required quantity and dates of a sales document to materials planning department.
Types of TOR :
TOR with individual requirement – Requirement based on each schedule line in sales order is transferred.
TOR with collective requirement – combine several requirement based on daily or weekly.
Collective requirement can be transferred according to following criteria:
- Plant, Batch, Storage Location, Date, Transaction, Requirement class.
The system creates individual requirement for special stocks even if collective requirement is specified.
Controlling element of TOR and Availability check:
Requirement class: the transfer of requirement must be switched on at requirement class level.
Requirement Type: the requirement type must exist which should determine requirement class.
Plant: A Plant must be defined at item level in sales order.
Checking Group: A checking group must be defined in the material master record. (Ex. 01 coll. Req. 02 Ind. Req.)
Schedule line Category: the TOR must be switched on at schedule line level.
Stock Requirement Display – MD04
It displays requirement of orders, schedule line its.
Availability Overview: CO09
Configuration:
- Define Requirement Class
- Define Requirement Type – just assign Req. type to Req. class.
- Determination of requirement types using transaction – how the req. type is determined in the document. “Item category + MRP type = Req. Type”
- Define procedure for each schedule line. Activate TOR and avail check for Schl. Line.(check box)
- Block quantity confirmation in delivery blocks – in delivery blocks we can blocks delivery creation for a different blocking reason. Means we can sale the sales order but can not create delivery unless we remove the delivery block. However it does not block the TOR and qty confirmation, but in certain block like due to Credit problem, we need to block the TOR and qty confirmation also so that quantity should not be confirmed for the sales order. That we define here for every reason whether we want to block the TOR also i.e. qty confirmation. In addition to that you can define the Days up to which you want to block the qty confirmation. Suppose it takes 10 days for you to clear the matter of customer credit problem, that you can put 10 days as difference period and after 10 days it will automatically transfer the requirement and will confirm the qty.
Standard req. class:
011 – Delivery Req.
030 – Sales from stock
031 – Order requirement
039 – Service Item
040 – Make to order
041 – order/deli. Req.
How the Requirement type is determined in Documents:
1. First, an attempt is made to find a requirements type using the strategy group in the material master.
2. If the strategy group has not been maintained, the system will determine it using the MRP group.
3. If the MRP group has not been defined, the system uses the material type instead of the MRP group when accessing the corresponding control tables.
4. If no requirements type is found here, the system assumes a special rule and attempts to find a requirements type with the aid of the item category and the MRP type.
5. If this is not possible, a last attempt is made to find a requirements type with the item category only.
6. If the last attempt fails, the system declares the transaction as not relevant for the availability check or transfer of requirements
Based on Requirement Type, system defines Requirement class.
Transfer of required quantity and dates of a sales document to materials planning department.
Types of TOR :
TOR with individual requirement – Requirement based on each schedule line in sales order is transferred.
TOR with collective requirement – combine several requirement based on daily or weekly.
Collective requirement can be transferred according to following criteria:
- Plant, Batch, Storage Location, Date, Transaction, Requirement class.
The system creates individual requirement for special stocks even if collective requirement is specified.
Controlling element of TOR and Availability check:
Requirement class: the transfer of requirement must be switched on at requirement class level.
Requirement Type: the requirement type must exist which should determine requirement class.
Plant: A Plant must be defined at item level in sales order.
Checking Group: A checking group must be defined in the material master record. (Ex. 01 coll. Req. 02 Ind. Req.)
Schedule line Category: the TOR must be switched on at schedule line level.
Stock Requirement Display – MD04
It displays requirement of orders, schedule line its.
Availability Overview: CO09
Configuration:
- Define Requirement Class
- Define Requirement Type – just assign Req. type to Req. class.
- Determination of requirement types using transaction – how the req. type is determined in the document. “Item category + MRP type = Req. Type”
- Define procedure for each schedule line. Activate TOR and avail check for Schl. Line.(check box)
- Block quantity confirmation in delivery blocks – in delivery blocks we can blocks delivery creation for a different blocking reason. Means we can sale the sales order but can not create delivery unless we remove the delivery block. However it does not block the TOR and qty confirmation, but in certain block like due to Credit problem, we need to block the TOR and qty confirmation also so that quantity should not be confirmed for the sales order. That we define here for every reason whether we want to block the TOR also i.e. qty confirmation. In addition to that you can define the Days up to which you want to block the qty confirmation. Suppose it takes 10 days for you to clear the matter of customer credit problem, that you can put 10 days as difference period and after 10 days it will automatically transfer the requirement and will confirm the qty.
Standard req. class:
011 – Delivery Req.
030 – Sales from stock
031 – Order requirement
039 – Service Item
040 – Make to order
041 – order/deli. Req.
How the Requirement type is determined in Documents:
1. First, an attempt is made to find a requirements type using the strategy group in the material master.
2. If the strategy group has not been maintained, the system will determine it using the MRP group.
3. If the MRP group has not been defined, the system uses the material type instead of the MRP group when accessing the corresponding control tables.
4. If no requirements type is found here, the system assumes a special rule and attempts to find a requirements type with the aid of the item category and the MRP type.
5. If this is not possible, a last attempt is made to find a requirements type with the item category only.
6. If the last attempt fails, the system declares the transaction as not relevant for the availability check or transfer of requirements
Based on Requirement Type, system defines Requirement class.
BF-Incompletion Log
Incompletion Log:
- Define Incompleteness Procedure
- Assign incompleteness Procedure
- Define status group
Incompleteness Objects – Incompleteness group:
- Sales – Header
- Sales – Item
- Sales – Schedule line
- Partner
- Sales activity
- Delivery Header
- Delivery Item
Incompleteness Procedure :
First we have Incompleteness Group like Sales – Header, under that we have Incompleteness Procedure like 10 – Inquiry , 11 – Order etc. in each procedure, we have fields which should be filled during the creation of the particular document. We can set the system, whether we want to give Error or Warning message. However in delivery no warning message can be given, we have to define error message only.
If we set warning message, we can save the document but cannot process further. If we set for error message, than we cannot save the document unless and until we provide the incomplete fields.
- Define Incompleteness Procedure
- Assign incompleteness Procedure
- Define status group
Incompleteness Objects – Incompleteness group:
- Sales – Header
- Sales – Item
- Sales – Schedule line
- Partner
- Sales activity
- Delivery Header
- Delivery Item
Incompleteness Procedure :
First we have Incompleteness Group like Sales – Header, under that we have Incompleteness Procedure like 10 – Inquiry , 11 – Order etc. in each procedure, we have fields which should be filled during the creation of the particular document. We can set the system, whether we want to give Error or Warning message. However in delivery no warning message can be given, we have to define error message only.
If we set warning message, we can save the document but cannot process further. If we set for error message, than we cannot save the document unless and until we provide the incomplete fields.
BF-Partner Determination
Partner Determination for customer Master (Acc grp), Sales Document Header (sales document type), Sales Document Item (Item type), Delivery (delivery type), shipment (shipment type), billing Header (billing document type), billing Item (billing document type), Sales Activity (Sales activity type).
Partner Determination:
Partner Type : KU – Customer, LI – Vendor, AP – contact person, PE – Personnel
Partner function : SP – sold to party, FA – forwarding agents, CP – contact person, SE – Sales employee
Mandatory Partner Function : Sold-to Party, ship-to Party, Bill-to Party, Payer
Customization:
Define Partner Function: we can use standard defined partner function available in SAP like Sold-to party, ship-to party etc. however we can define our own partner functions also. For new :
Partner Func – Name – Partner Type – error – sup. Part. Func. – Uniqueness – cust. Hier. Type
SP sold-to KU 07 Select
Define Partner function Procedure and assign allowed partner function to it. We have standard partner procedures available like:
- AG – sold-to Party (for customer master)
- TA – standard Order (Sales Header)
- N – standard Item
- LF – Delivery note
- TR – shipment header gen.
- FK – billing Document
- FP – Billing Item
Assignment –
Part. Procedure – Parnter Function – Not modifiable – Mandatory function
AG SP Select Select
AG BP Select
Partner Determination Procedure assignment:
We assign the procedure to acc grp(for customer master), Order type (For sales header), Sales Item category(for Sales Item), Delivery type (For delivery), Billing type (for billing header & item).
Account group – Partner function assignment:
Assign allowed partner function for each customer account group.
Partner Determination:
Partner Type : KU – Customer, LI – Vendor, AP – contact person, PE – Personnel
Partner function : SP – sold to party, FA – forwarding agents, CP – contact person, SE – Sales employee
Mandatory Partner Function : Sold-to Party, ship-to Party, Bill-to Party, Payer
Customization:
Define Partner Function: we can use standard defined partner function available in SAP like Sold-to party, ship-to party etc. however we can define our own partner functions also. For new :
Partner Func – Name – Partner Type – error – sup. Part. Func. – Uniqueness – cust. Hier. Type
SP sold-to KU 07 Select
Define Partner function Procedure and assign allowed partner function to it. We have standard partner procedures available like:
- AG – sold-to Party (for customer master)
- TA – standard Order (Sales Header)
- N – standard Item
- LF – Delivery note
- TR – shipment header gen.
- FK – billing Document
- FP – Billing Item
Assignment –
Part. Procedure – Parnter Function – Not modifiable – Mandatory function
AG SP Select Select
AG BP Select
Partner Determination Procedure assignment:
We assign the procedure to acc grp(for customer master), Order type (For sales header), Sales Item category(for Sales Item), Delivery type (For delivery), Billing type (for billing header & item).
Account group – Partner function assignment:
Assign allowed partner function for each customer account group.
Friday, January 29, 2010
Special Master Data
Special Master data : for Sales tools.
- Customer Material info record
- Item Proposal
- Listing & Exclusion
- Product substitution
Customer Material Information Record – VD51
- Defines customer alias for material and description.
- Can further define attributes of material, shipping and partial delivery information specific to customer and material.
Item / Product Proposal VA51
PV – Item proposal
MS – Product proposal
It is defined in order type.
- Used to define frequently ordered combination or special assortment of products and quantities.
- Either products or products with quantity can be selected during order entry.
- An item proposal is assigned in customer master data.
Master record for Item Proposal:
VA51 - Provide sales area and Provide Item proposal type PV Item proposal, MV – Product proposal, Provide validity period, enter materials with Qty. Save.
Note down the Number and assign the same in customer master record in Sales area data – Sales tab – Item proposal. In sales order we have to select the button “Propose Item”.
Material Listing & Exclusion: VB01
Used to what products are available for a customer or group.
It is customized by condition Techniques.
Customer Listing: customer receives only specific materials. If the sold-to-party is different than the payer in the sales order and if both partners have master records, the system first search for the sold to party’s master record. If it finds valid master record, it stops searching. Any records listed for payer are not taken into consideration. If the first search is not successful, the system searches for the payer’s master records.
Material Exclusion: Ensures that customer does not receive certain materials. If the sold to party is different than the payer in the sales order and both partner have master records, the system searches first for the sold-to party’s records. If the system finds a valid record, the reference to the material is prevented and system stop searching. It does not check the payer’s master record. If the first search is unsuccessful, the system searches for the payer’s master record.
Product substitution / Material Determination / Product Selection.
It is based on condition techniques.
Configuration:
- Maintain prerequisite for Material determination. Maintain access seq. condition type, procedure. Standard is A00001 – A001
- Assign Procedure to Sales document type OR – A00001
- Define substitute reason. Here you define following things:
o Substitute reason and its description
o Entry checkbox – it indicates whether the system prints the name of the original material in the output.
o Warning checkbox – it indicates whether the system display a warning message before substituting the material.
o Strategy: it controls whether the material should be substituted automatically or the selection list should be displayed.
Space – Automatic, A – substitute products are displayed for selection (Manual)
o Outcome – control whether the outcome of product selection should replace the original entry or it should be recorded as sub item of the original entry.
Space – Item will be replaced.
A – Substitution products are displayed as sub items.
B – As in A but only when creating item in sales.
If you select A than in delivery again substitution will be carry out and if at that time substitute products are not available than main item or other substitute products will be delivered.
If you select B than the substitute product selected in sales order will be copied into the delivery.
Standard item categories ate TAX (Main item) and TAPS (sub item). Here pricing and availability check will be carried out at sub item. However if you want to carry out pricing at main item, than make necessary changes in main item i.e make it relevant for pricing and for sub item make it for Not relevant for pricing.
Schedule line categories are CX and PP respectively.
Enables automatic or manual substitution of materials during sales order processing.
You can assign substitute reason to every master record in material determination that defines how the material should be determined. You define substitute rules in customizing.
You do not need a material master record for the material you are entering.
The Item Overview of Sales A contains information about the material that was originally entered as well as the reason for substitution.
Reason 0005 – Manual Product Selection (List of default values)
Reason 0004 / 0006 – Automatic product selection (Depending on availability in order and delivery)
In Manual Selection – it displays a list of all substitute materials and other information in master records. To simplify selection, the system displays the material quantity that can be confirmed on requested delivery date. If not than it displays the possible date the material will be available.
In automatic product selection, the system replaces the entered material automatically if it is not available. In automatic selection, based on customizing, the system may display the entered and substitute material as main item and sub-items in sales order.
When you enter the material in sales order it replaces with the first material in the selection master record. But suppose required quantity is 10 and the first materials has 4 qty available, than it will select the second material in the master record and fills the remaining qty with the second material.
We can choose whether we want to re-run the material determination in delivery or not.
You can use the product attributes in material and customer master records to exclude a particular material from product selection. This means for example that all the materials that have been rejected in the customer master will not be included by the system when it determines the substitution material.
The sequence of substitute materials in master data influences the result of the automatic product selection in the order.
If you want the material originally entered in the sales order to be included in the substitution, than you must enter it in the substitution list. Here now we can have two scenarios:
- If the original material is at the first place in the list and its available stock is included in the substitution. Than the system refers to the available stock of the next material in the master record.
- If the material originally entered in the sales order, is not in the first place of the substitution list, the system uses up the available stock of the materials that appears in the master records before the material that originally entered.
- Customer Material info record
- Item Proposal
- Listing & Exclusion
- Product substitution
Customer Material Information Record – VD51
- Defines customer alias for material and description.
- Can further define attributes of material, shipping and partial delivery information specific to customer and material.
Item / Product Proposal VA51
PV – Item proposal
MS – Product proposal
It is defined in order type.
- Used to define frequently ordered combination or special assortment of products and quantities.
- Either products or products with quantity can be selected during order entry.
- An item proposal is assigned in customer master data.
Master record for Item Proposal:
VA51 - Provide sales area and Provide Item proposal type PV Item proposal, MV – Product proposal, Provide validity period, enter materials with Qty. Save.
Note down the Number and assign the same in customer master record in Sales area data – Sales tab – Item proposal. In sales order we have to select the button “Propose Item”.
Material Listing & Exclusion: VB01
Used to what products are available for a customer or group.
It is customized by condition Techniques.
Customer Listing: customer receives only specific materials. If the sold-to-party is different than the payer in the sales order and if both partners have master records, the system first search for the sold to party’s master record. If it finds valid master record, it stops searching. Any records listed for payer are not taken into consideration. If the first search is not successful, the system searches for the payer’s master records.
Material Exclusion: Ensures that customer does not receive certain materials. If the sold to party is different than the payer in the sales order and both partner have master records, the system searches first for the sold-to party’s records. If the system finds a valid record, the reference to the material is prevented and system stop searching. It does not check the payer’s master record. If the first search is unsuccessful, the system searches for the payer’s master record.
Product substitution / Material Determination / Product Selection.
It is based on condition techniques.
Configuration:
- Maintain prerequisite for Material determination. Maintain access seq. condition type, procedure. Standard is A00001 – A001
- Assign Procedure to Sales document type OR – A00001
- Define substitute reason. Here you define following things:
o Substitute reason and its description
o Entry checkbox – it indicates whether the system prints the name of the original material in the output.
o Warning checkbox – it indicates whether the system display a warning message before substituting the material.
o Strategy: it controls whether the material should be substituted automatically or the selection list should be displayed.
Space – Automatic, A – substitute products are displayed for selection (Manual)
o Outcome – control whether the outcome of product selection should replace the original entry or it should be recorded as sub item of the original entry.
Space – Item will be replaced.
A – Substitution products are displayed as sub items.
B – As in A but only when creating item in sales.
If you select A than in delivery again substitution will be carry out and if at that time substitute products are not available than main item or other substitute products will be delivered.
If you select B than the substitute product selected in sales order will be copied into the delivery.
Standard item categories ate TAX (Main item) and TAPS (sub item). Here pricing and availability check will be carried out at sub item. However if you want to carry out pricing at main item, than make necessary changes in main item i.e make it relevant for pricing and for sub item make it for Not relevant for pricing.
Schedule line categories are CX and PP respectively.
Enables automatic or manual substitution of materials during sales order processing.
You can assign substitute reason to every master record in material determination that defines how the material should be determined. You define substitute rules in customizing.
You do not need a material master record for the material you are entering.
The Item Overview of Sales A contains information about the material that was originally entered as well as the reason for substitution.
Reason 0005 – Manual Product Selection (List of default values)
Reason 0004 / 0006 – Automatic product selection (Depending on availability in order and delivery)
In Manual Selection – it displays a list of all substitute materials and other information in master records. To simplify selection, the system displays the material quantity that can be confirmed on requested delivery date. If not than it displays the possible date the material will be available.
In automatic product selection, the system replaces the entered material automatically if it is not available. In automatic selection, based on customizing, the system may display the entered and substitute material as main item and sub-items in sales order.
When you enter the material in sales order it replaces with the first material in the selection master record. But suppose required quantity is 10 and the first materials has 4 qty available, than it will select the second material in the master record and fills the remaining qty with the second material.
We can choose whether we want to re-run the material determination in delivery or not.
You can use the product attributes in material and customer master records to exclude a particular material from product selection. This means for example that all the materials that have been rejected in the customer master will not be included by the system when it determines the substitution material.
The sequence of substitute materials in master data influences the result of the automatic product selection in the order.
If you want the material originally entered in the sales order to be included in the substitution, than you must enter it in the substitution list. Here now we can have two scenarios:
- If the original material is at the first place in the list and its available stock is included in the substitution. Than the system refers to the available stock of the next material in the master record.
- If the material originally entered in the sales order, is not in the first place of the substitution list, the system uses up the available stock of the materials that appears in the master records before the material that originally entered.
Wednesday, January 27, 2010
Master Data
Master Data:
Master data is pool of data which are created centrally in the system and available for every document whenever they want to access the data.
Data origin in Sales documents:
- Customer Master
- Material Master
- Customer-material info record
- Conditions Records (Pricing, Output, Cross Sales, Free Goods, Material determination,
Customer Master:
General Data: Relevant for SD and accounting. Tabs:
- Address
o Title, Name, Search term, Street, City, Pincode, country, Region, timezone, transportation zone, Language,
- Control data
o Vendor, VAT reg no
- Payment Transaction
o Bank details
- Marketing
o Nielson ID, Customer class, Industry, annual sales, no of employee, Legal status, fiscal year variant,
- Unloading Points
o Unloading point, Receiving point, Calendar, Customer calendar, goods receiving hours
- Export data
- Contact Persons
o Name, home address, visiting hours, Partner function
Sales Area data:
- Orders
o Sales district, Sales office, Sales grp, customer grp, Order probability, Item proposal, currency,
o Price grp, customer Pricing procedure, Price list, Customer statistic grp,
- Shipping
o Delivery priority, Order combination, Shipping condition, Delivering plant, Completer delivery req, max partial delivery, Tolerance,
- Billing document
o Rebate, Price determination, Invoicing dates, Invoicing list dates, Inco terms, Terms of Payment, Credit control area, Acc assignment group,
o Country, Tax category, tax classification
- Documents
- Partner functions.
Company Code Data:
- Account Management
o Reconciliation account, Cash management grp,
- Payment Transaction
o Terms of Payment, Payment History record
- Correspondence – dunning prcedure
- Insurance
Effects of changes in Customer Master data:
When you change the master data after having used it for creating document, its changes do not affect the document created. However Address is an exception. Means new address will be reflected in the old documents also.
Account groups in customer Master:
It determines which fields are to be used in defining customer master. Depending upon the partner function and transaction, we assign or change the field status(Optional, Mandatory, Display, Suppressed) . Depending upon the field status system prevents the particular field in the customer master while maintaining customer master.
Mandatory Business Partners:
Sold-to-Party
Bill-to-Party
Ship-to-Party
Payer
Organization unit in customer Master:
- Company Code
- Sales Organization
- Distribution channel
- Division
Material Master:
It is grouped in several views. Like
- General data 1 and 2
o UOM, Gross Weight, Net weight, division, Gen Item cat grp, Weigh unit
o xPlant material status
- Classification
- Sales – Sales org - 1
o Basic UOM, division, Material group, Sales unit, Delivering plant, sales discount
o Country, tax category, Tax classification(liable or except)
o Mini Order qty, Min Deli qty, Delivery unit, Dist channel specific status
- Sales – Sales org - 2
o Material Statistic grp, Material Pricing grp, Volume Rebate grp, acc assignment grp, Item category Grp
- Sales : General/Plant Data
o Base unit, Gross Weight, Net weight, Avail. Check, Batch management,
o Transportation grp, Loading grp.
- Foreign trade/Export
- Purchasing
- MRP 1 – 2 - 3 – 4
o MRP grp, MRP Type, MRP controller, Lot size
o Procurement type, In-house production time, Planned delivery days, SchMargin Key
o Strategy grp, Availability check, Total RLT time
- Accounting 1 -2
o Valuation category, Valuation class, Price control, Price unit, Moving price, Standard price,
- Costing
Organization unit in Material Master:
- Plant
- Storage Location
- Sales Organization
- Distribution channel
-
Cross-division sales:
Here header division can differ with division of other material entered in sales order. We can control this in customization of sales document :
- Check division – Whether it is possible to enter multiple material with different division(different then the header division). We can set it in document type whether it should show error message, dialog or no dialog.
- Item division - whether the division in material master is copied in the document or the division in header also copied in to the item level. If we select this checkbox, then division from material master will be proposed in the item.
Division specific sales: If you set the Check Division for Error message, then it becomes division specific sales, and we can n not enter material from different division and which differs from the header division.
Condition Master:
Pricing condition:
For Pricing component – Price, Discount & Surcharge, Freight and Tax.
The condition type defines multiple use of condition.
You can have a percentage, a quantity dependent or an amount dependent surcharge or discount.
By specifying validity period, you can restrict a price agreement to a certain period.
We can maintain values within a condition record according to a scale.
Shared Master data Concept:
We define common DS and DIV to share master data of common DS and DIV with other DS and DIV.
On the sales org/Distribution channel level we can define which distribution channel should be used to accessing the condition records and which should be used for customer and material master.
On the Sales org/Division level, we can define which division should be used to accessing the condition record and which should be used for customer master.(not material master)
It is not possible to define shared master data for sales organization.
Shared Master data and SIS:
Even if you are using shared master data, the data values transferred to SIS comes from values in sales documents.
For multi-division sales you must specify the correct source field for the division in SIS so that this setting affects the updating rules in the SIS. i.e. MCVBAK-SPART or MCVBAP-SPART.
Master data is pool of data which are created centrally in the system and available for every document whenever they want to access the data.
Data origin in Sales documents:
- Customer Master
- Material Master
- Customer-material info record
- Conditions Records (Pricing, Output, Cross Sales, Free Goods, Material determination,
Customer Master:
General Data: Relevant for SD and accounting. Tabs:
- Address
o Title, Name, Search term, Street, City, Pincode, country, Region, timezone, transportation zone, Language,
- Control data
o Vendor, VAT reg no
- Payment Transaction
o Bank details
- Marketing
o Nielson ID, Customer class, Industry, annual sales, no of employee, Legal status, fiscal year variant,
- Unloading Points
o Unloading point, Receiving point, Calendar, Customer calendar, goods receiving hours
- Export data
- Contact Persons
o Name, home address, visiting hours, Partner function
Sales Area data:
- Orders
o Sales district, Sales office, Sales grp, customer grp, Order probability, Item proposal, currency,
o Price grp, customer Pricing procedure, Price list, Customer statistic grp,
- Shipping
o Delivery priority, Order combination, Shipping condition, Delivering plant, Completer delivery req, max partial delivery, Tolerance,
- Billing document
o Rebate, Price determination, Invoicing dates, Invoicing list dates, Inco terms, Terms of Payment, Credit control area, Acc assignment group,
o Country, Tax category, tax classification
- Documents
- Partner functions.
Company Code Data:
- Account Management
o Reconciliation account, Cash management grp,
- Payment Transaction
o Terms of Payment, Payment History record
- Correspondence – dunning prcedure
- Insurance
Effects of changes in Customer Master data:
When you change the master data after having used it for creating document, its changes do not affect the document created. However Address is an exception. Means new address will be reflected in the old documents also.
Account groups in customer Master:
It determines which fields are to be used in defining customer master. Depending upon the partner function and transaction, we assign or change the field status(Optional, Mandatory, Display, Suppressed) . Depending upon the field status system prevents the particular field in the customer master while maintaining customer master.
Mandatory Business Partners:
Sold-to-Party
Bill-to-Party
Ship-to-Party
Payer
Organization unit in customer Master:
- Company Code
- Sales Organization
- Distribution channel
- Division
Material Master:
It is grouped in several views. Like
- General data 1 and 2
o UOM, Gross Weight, Net weight, division, Gen Item cat grp, Weigh unit
o xPlant material status
- Classification
- Sales – Sales org - 1
o Basic UOM, division, Material group, Sales unit, Delivering plant, sales discount
o Country, tax category, Tax classification(liable or except)
o Mini Order qty, Min Deli qty, Delivery unit, Dist channel specific status
- Sales – Sales org - 2
o Material Statistic grp, Material Pricing grp, Volume Rebate grp, acc assignment grp, Item category Grp
- Sales : General/Plant Data
o Base unit, Gross Weight, Net weight, Avail. Check, Batch management,
o Transportation grp, Loading grp.
- Foreign trade/Export
- Purchasing
- MRP 1 – 2 - 3 – 4
o MRP grp, MRP Type, MRP controller, Lot size
o Procurement type, In-house production time, Planned delivery days, SchMargin Key
o Strategy grp, Availability check, Total RLT time
- Accounting 1 -2
o Valuation category, Valuation class, Price control, Price unit, Moving price, Standard price,
- Costing
Organization unit in Material Master:
- Plant
- Storage Location
- Sales Organization
- Distribution channel
-
Cross-division sales:
Here header division can differ with division of other material entered in sales order. We can control this in customization of sales document :
- Check division – Whether it is possible to enter multiple material with different division(different then the header division). We can set it in document type whether it should show error message, dialog or no dialog.
- Item division - whether the division in material master is copied in the document or the division in header also copied in to the item level. If we select this checkbox, then division from material master will be proposed in the item.
Division specific sales: If you set the Check Division for Error message, then it becomes division specific sales, and we can n not enter material from different division and which differs from the header division.
Condition Master:
Pricing condition:
For Pricing component – Price, Discount & Surcharge, Freight and Tax.
The condition type defines multiple use of condition.
You can have a percentage, a quantity dependent or an amount dependent surcharge or discount.
By specifying validity period, you can restrict a price agreement to a certain period.
We can maintain values within a condition record according to a scale.
Shared Master data Concept:
We define common DS and DIV to share master data of common DS and DIV with other DS and DIV.
On the sales org/Distribution channel level we can define which distribution channel should be used to accessing the condition records and which should be used for customer and material master.
On the Sales org/Division level, we can define which division should be used to accessing the condition record and which should be used for customer master.(not material master)
It is not possible to define shared master data for sales organization.
Shared Master data and SIS:
Even if you are using shared master data, the data values transferred to SIS comes from values in sales documents.
For multi-division sales you must specify the correct source field for the division in SIS so that this setting affects the updating rules in the SIS. i.e. MCVBAK-SPART or MCVBAP-SPART.
SD In Brief
SD in Brief:
- Enterprise Structure
- Master data
- Sales
- Shipping
- Billing
- Sales info system
- Transportation
- Sales support
- Foreign Trade
Enterprise structure:
IDES means: Internet Demonstration and Evaluation System.
SD Organization units:
- Company code
- Sales area
o Sales Organization
o Distribution channel
o Division
- Plant
- Storage Location
- Shipping Point
- Sales Office
- Sales Group
- Sales Personals
Sales Line: Sales organization – distribution channel – Plant
Definitions:
Company Code: a complete independent accounting unit, represented as smallest organizational unit in external accounting.
Sales Organization: it is unit in logistic which groups the enterprise according to the requirement of sales and distribution. It has its own master data for customer, material and conditions and did not share it master data with other sales organization. it is responsible for distribution goods and services, for negotiating sales, carry out each business transaction.
Distribution channel: it is a means through which material or service reaches to customers. We can create master data for customer, material or conditions.
Division: it represents a product line. We can have master data for customer and conditions. ( not for material master).
Sales area: it defines the distribution channel, a sales organization uses to sell products from a certain division.
Plant: the plant is location where materials are kept. In R/3, plant can represent a production facility or simply grouping of locations (Storage location) in physical proximity.
Shipping Point: Highest organizational unit in Shipping that controls all shipping activity. A shipping point can be a loading ramp, a mail depot, or a rail depot. It can also be a group of employees responsible only for urgent deliveries. A shipping point is physical place and should be near to delivering plant. One shipping point can belongs to several plant and one plant can have several shipping point.
It is decided in sales order based on Plant, shipping condition and loading group.
- Enterprise Structure
- Master data
- Sales
- Shipping
- Billing
- Sales info system
- Transportation
- Sales support
- Foreign Trade
Enterprise structure:
IDES means: Internet Demonstration and Evaluation System.
SD Organization units:
- Company code
- Sales area
o Sales Organization
o Distribution channel
o Division
- Plant
- Storage Location
- Shipping Point
- Sales Office
- Sales Group
- Sales Personals
Sales Line: Sales organization – distribution channel – Plant
Definitions:
Company Code: a complete independent accounting unit, represented as smallest organizational unit in external accounting.
Sales Organization: it is unit in logistic which groups the enterprise according to the requirement of sales and distribution. It has its own master data for customer, material and conditions and did not share it master data with other sales organization. it is responsible for distribution goods and services, for negotiating sales, carry out each business transaction.
Distribution channel: it is a means through which material or service reaches to customers. We can create master data for customer, material or conditions.
Division: it represents a product line. We can have master data for customer and conditions. ( not for material master).
Sales area: it defines the distribution channel, a sales organization uses to sell products from a certain division.
Plant: the plant is location where materials are kept. In R/3, plant can represent a production facility or simply grouping of locations (Storage location) in physical proximity.
Shipping Point: Highest organizational unit in Shipping that controls all shipping activity. A shipping point can be a loading ramp, a mail depot, or a rail depot. It can also be a group of employees responsible only for urgent deliveries. A shipping point is physical place and should be near to delivering plant. One shipping point can belongs to several plant and one plant can have several shipping point.
It is decided in sales order based on Plant, shipping condition and loading group.
Saturday, January 16, 2010
SAP ERP
About SAP & ERP
ERP makes management reporting and decision making fast and easy.
Managing 4 M’s of the organization.
- Man
- Money
- Machine
- Material
MRP developed in 1970, which involved planning of materials according to the production schedule.
Package Evolution:
SAP, Oracle, Siebel, People Soft, JD Edwards, BAAN,
Benefits:
Improve business performance
Support business growth requirement – new product, new market,
Provide integrated real time system
Eliminate limitations in legacy system.
All data are available in central database.
Eliminate data redundancy.
Data is updated and available real time.
SAP
Systems Applications and Products in data processing.
Founded in 1972 by 5 former IBM employee. Head office at Walldorf, Germany.
It is table driven customizing software.
Version:
SAP R/1 - 1972
SAP R/2 - 1979
SAP R/3 - 1992
SAP R/3 4.6B
SAP R/3 4.6C
SAP R/3 4.7C
SAP R/3 4.7EE (Enterprise Edition)
ECC 5.0 (mySAP ERP 2004s)
ECC 6.0 (mySAP ERP 2005s)
ECC – ERP central component)
mySAP Business Suit Contains:
mySAP ERP
mySAP CRM
mySAP PLM
mySAP SRM
mySAP SCM
All the above packages are developed on SAP NetWeaver.
Benefits of SAP
- Multilingual
- Multi currency
- Multi company
R/3 Architecture:
Presentation Layer -àSAP GUI
Application server -àR/3 server component
Database Layer à Actual database
All this can be on same machine or can be on different machines. If different then TCP/IP software joins the layer together.
SAP system Landscape:
Three different environment:
- Development client
- Quality client
- Production client
For each client, we will have Presentation Layer, Application Layer, Database Layer.
Networking is handled by combination of VSAT and Leased Lines or VPN.
Data transfer from one client to other client is done through Transport Request.
Projects in SAP:
Three teams:
- Implementation team.
- Client Core team
- Client Power users.
ASAP Methodology:
- Project Preparation
- Business blueprint
- Realization
- Final Preparation.
- Go-Live and support
Types of Projects:
- Implementation (Big bang)
- Roll Outs (Phase wise)
- Production support and maintenance.
ERP makes management reporting and decision making fast and easy.
Managing 4 M’s of the organization.
- Man
- Money
- Machine
- Material
MRP developed in 1970, which involved planning of materials according to the production schedule.
Package Evolution:
SAP, Oracle, Siebel, People Soft, JD Edwards, BAAN,
Benefits:
Improve business performance
Support business growth requirement – new product, new market,
Provide integrated real time system
Eliminate limitations in legacy system.
All data are available in central database.
Eliminate data redundancy.
Data is updated and available real time.
SAP
Systems Applications and Products in data processing.
Founded in 1972 by 5 former IBM employee. Head office at Walldorf, Germany.
It is table driven customizing software.
Version:
SAP R/1 - 1972
SAP R/2 - 1979
SAP R/3 - 1992
SAP R/3 4.6B
SAP R/3 4.6C
SAP R/3 4.7C
SAP R/3 4.7EE (Enterprise Edition)
ECC 5.0 (mySAP ERP 2004s)
ECC 6.0 (mySAP ERP 2005s)
ECC – ERP central component)
mySAP Business Suit Contains:
mySAP ERP
mySAP CRM
mySAP PLM
mySAP SRM
mySAP SCM
All the above packages are developed on SAP NetWeaver.
Benefits of SAP
- Multilingual
- Multi currency
- Multi company
R/3 Architecture:
Presentation Layer -àSAP GUI
Application server -àR/3 server component
Database Layer à Actual database
All this can be on same machine or can be on different machines. If different then TCP/IP software joins the layer together.
SAP system Landscape:
Three different environment:
- Development client
- Quality client
- Production client
For each client, we will have Presentation Layer, Application Layer, Database Layer.
Networking is handled by combination of VSAT and Leased Lines or VPN.
Data transfer from one client to other client is done through Transport Request.
Projects in SAP:
Three teams:
- Implementation team.
- Client Core team
- Client Power users.
ASAP Methodology:
- Project Preparation
- Business blueprint
- Realization
- Final Preparation.
- Go-Live and support
Types of Projects:
- Implementation (Big bang)
- Roll Outs (Phase wise)
- Production support and maintenance.
Subscribe to:
Posts (Atom)