Learning SD Module

Hi Friends,
though I am ABAPer, I want to learn the SD Module.
Plz help in telling the useful links where I can get gud learning documents or plz tell me how to start with the basics of SD Module.
Waiting for ur replies.
Nishu

i think this would be helpful for u little bit
http://big4guy.com/index.php?cat=31
http://help.sap.com/saphelp_47x200/helpdata/en/92/df293581dc1f79e10000009b38f889/frameset.htm
http://www.sap.com/services/education/index.epx
http://www.sap-img.com/sap-sd.htm
For transaction codes check the following link.
http://www.sapgenie.com/saptech/transactions.htm#tx
For SAP SD tables
http://www.sapgenie.com/abap/tables_sd.htm
http://www.sap-basis-abap.com/sapsd.htm
http://www.sapgenie.com/abap/tables_sd.htm
http://help.sap.com/saphelp_46c/helpdata/en/8c/df293581dc1f79e10000009b38f889/frameset.htm
you can find SD reports in the SAP menu under
Logistics -> Sales and Distribution -> Sales Information System -> Information System
and i am having some more material if u can mail me i will send it to u
i will these links would be helpful for u

Similar Messages

How to learn MM module basics and SD module

Hi all,
As abapers you all need some basic knowledge of the modules, for example I need the info of the modules MM and SD, because I generally get works from these two module and I do not know much on them...
How to learn these modules basics without having to any course?
Could you please provide me documents if possible; my email is : [email protected]
Thank you very much

Hi Deniz,
Process Summaries
Create Sales Order
1.     Use Transaction Code VA01
2.     Identify Sales Office
3.     Enter Sold-to-party (customer) and purchase order number and date if applicable
4.     Enter material, quantity and rate
5.     Credit income to account (Internal Order or WBS element)
6.     Enter partner (University contact details)
7.     Save Sales Order
Create Billing Document
1.     Directly after saving the Sales Order, follow the path Sales document> Billing.
2.     Save the billing document
Other than as a follow-on function
1.     Use Transaction Code VF01
2.     The sales order number will default in check that it is correct
3.     Save the Billing document
Print a Billing document immediately
1.     Use transaction code VF03
2.     Enter the Billing Document number.
3.     Follow path Issue Output to > Printer
4.     Click on execute twice
5.     To preview, follow the path Issue Output to > Screen and click on execute twice to view
Document Flow
1.     Use transaction code VA03 (Sales Order/Credit Memo or VF03 (Billing document) or
2.     Follow the path Environment > Document Flow
3.     Enter the document number
4.     Click on the document overview icon
Common Transaction Codes
Access to transactions is limited by your security profile
For easier access, add transactions to your favourites folders
Create Sales Order     VA01
Create Credit Memo     VA01
Change Sales Order     VA02
Display Sales Order     VA03
List Sales Order     VA05
Create Billing Doc     VF01
Display Billing Doc     VF03
Cancel Billing Doc     VF11
Print Billing Doc     VF03
Display Customer     XD03
Display Material     MM03
Display Customer Line Items          FBL5
Document Structure
Numbering Range
80000000 89999999 Sales Orders
90000000 99999999 Billing Document
60000000 69999999 Credit Notes
800000 899999 Customers
2000000 - 2999999 Materials
for any further info check this link
http://www.leeds.ac.uk/iss/infosystems
Hope this helps u..
Reward points if useful..
Regards,
Sreenivas

How to learn SD Module

Hi guys,
I am a rookie to the R/3. to be honest i just learn a little of ABAP programming. Well, they force me to research on the SD Module. I don't think it's an easy thing for me. So my question is :
1. where to start my journey?
2. what kind of stuff should i take a look at.
PS. there are a lot of learning material there, i can hardly to read them all in time. So could you guys to suggest me some?
Any help will be appreciated.
Thanks in advance.
Jacob

dear jacob
since u know ABAP programming its bit easy to learn other modules and SD is one of that
here am sending all config about SD . go through this and Glenn C Williams book is a bible for SD go through that
all the best
ENTERPRISE STRUCTURE
Company Code: - It is the company for which we implement SAP.
NOTE: - It is defined by FI Consultants.
Sales Organisation: - It is the organizational unit, which is responsible for the sales activities in the company.
Distribution Channel: - It is the channel through which goods are reaching the customers.
Divisions: - The range of products or services that the company manufacturing falls into different divisions.
Sales Area: - It is the combination of sales Organisation, distribution channel and Division.
Sales Line: - It is the combination of Sales Organisation and distribution channel.
Sales Office: - It is the Geographical aspect of the structure.
Sales Group: - The employees in a sales office can be divided into different sales groups.
Plant: - The factory is called the plant in SAP.
RELATIONSHIPS:
Company code to Sales Organisation: - One company code can have many sales organizations. But one Organisation has to be assigned to one company code. So the relation is one to many.
Sales Organisation to Distribution channel: - One Organisation can have many distribution channels. One Distribution channel can be assigned to many organizations, so the relation is Many to Many.
Sales Organisation to Division: - One Organisation can have many divisions. One division can be assigned to many organizations. So the relationship is Many to Many.
Distribution channel to Division: - One Distribution channel can have many divisions. One division can be assigned to many Distribution channels. So the relationship is Many to Many.
NOTE: - Division is always Organisation specific.
NOTE: - If sales Organisation wants to use a plant that plant must be
assigned to the Sales Organisation.
Logistics
Sales and Distribution
Basic Function and Master Data in Sales and Distribution
Master data in Sales and Distribution
Organisational Structures
Organisational Structures in Sales and Distribution
Defining Sales Organisation: -
SPRO
Enterprise Structure
Definition
Sales and Distribution
Define Copy, Delete, Check Sales organization [EC04]
Go to Define Copy, Delete, Check Sales organization,
Go to Copy Organisational Object,
Come back
Define Sales Organisation
Select defined sales Organisation and go to details.
Select the Address icon & maintain the details and save it.
NOTE: - To unlock the locked data use the Transaction code SM12.
Rebate Process Active: - It controls whether rebate processing is active for a particular sales Organisation.
Defining Distribution Channel: -
SPRO
Enterprise Structure
Definition
Sales and Distribution
Define Copy, Delete, Check Distribution Channel [EC05]
Go to Define Copy, Delete, Check Distribution Channel
Go to Copy Organisational Object,
Come back
Go to Define Distribution Channel
Select defined sales Organisation and give the required name and save it.
Defining Division: -
SPRO
Enterprise Structure
Definition
Sales and Distribution
Define Copy, Delete, Check Division [EC06]
Go to Define Copy, Delete, Check Division
Go to Copy Organisational Object,
Come back
Go to Define Division
Select defined division and give the required name and save it.
Defining Sales Office: -
SPRO
Enterprise Structure
Definition
Sales and Distribution
Maintain Sales Office
Go to New entries and define the sales office
Go to Address Icon and maintain the details and save it.
Defining Sales Group: -
SPRO
Enterprise Structure
Definition
Sales and Distribution
Maintain Sales Group
Go to New entries and define the Sales Group
Go to Address Icon and maintain the details and save it.
Defining a Plant: -
SPRO
Enterprise Structure
Definition
Logistics General
Define, Copy, Delete, Check Plant [EC02]
Go to copy organisational object
Come back
Go to Define Plant
Select the defined Plant and go to details Address and Maintain Details and Edit details and save it.
Defining Company Code: -
SPRO
Enterprise Structure
Definition
Financial Accounting
Edit Copy, Delete, Check Company code [EC01]
Go to Define Company and save it.
Assigning Sales Organisation to the Company Code: -
SPRO
Enterprise Structure
Assignment
Sales and Distribution
Assign Sales Organisation to Company Code [OVX3]
Select the Company Code and go to assign from the list of sales Organisations and select required Sales Organisations and assign and save it.
Assigning Distribution Channels to Sales Organisations: -
SPRO
Enterprise Structure
Assignment
Sales and Distribution
Assign Distribution Channels to Sales Organisation [OVXK]
Select the Sales Organisation and go to assign from the list of the Distribution Channels and select required Distribution Channels and assign and save it.
Assigning Division to Sales Organisations: -
SPRO
Enterprise Structure
Assignment
Sales and Distribution
Assign Division to Sales Organisation [OVXA]
Select the Sales Organisation and go to assign from the list of the Divisions and select required Divisions and assign and save it.
Defining Sales area: -
SPRO
Enterprise Structure
Assignment
Sales and Distribution
Setup Sales area [OVXG]
Select the Sales Organisation and assign Distribution channels
Select the distribution channel and assign the divisions and save it.
Assigning Sales Office to Sales area: -
SPRO
Enterprise Structure
Assignment
Sales and Distribution
Assign Sales Office to Sales are [OVXM]
Select the required Sales Area and assign the Sales Office.
Assigning the Plant to the Company Code: -
SPRO
Enterprise Structure
Assignment
Logistics General
Assign Plant to Company code [OX18]
Select the Company code and assign the required Plants.
Assigning the Plant to Sales Organisation: -
SPRO
Enterprise Structure
Assignment
Sales and Distribution
Assign Sales Organisation Distribution Channel Plant [OVX6]
Select the required sales line and assign the required Plants.
2. MASTER DATA (MD)
Master Data is divided into:
Customer Master Data
Material Master Data
Conditions Master Data
Customer Material Information Record
1. Customer Master Data: -
Logistics
Sales and Distribution
Master Data
Business Partner
Customer
Create
XD01 Complete
Change
XD02 Change
Display
XD03 Display
The Customer Master Data contains 3 screens:
a. General Data
b. Company Code Data
c. Sales Area Data
Each screen contains different tab pages; each tab page contains different fields.
a. General Data screen: -
Marketing Tab Page: -
Customer Classification: - Specifies a classification of the customer for
Ex: - classifies the customer as a bulk buyer or it can be based on turnover.
Defining Customer Classification: -
SPRO
Sales and Distribution
Master data
Business Partner
Customers
Marketing
Define Customer Classifications
Go to new entries and define and save it.
Unloading Points Tab page: -
Unloading Point: - Specifies the point at which the material is to be unloaded.
Goods Receiving Hours: - Specifies the timings in which the customer can receive the goods.
Defining Goods Receiving Hours: -
SPRO
Sales and Distribution
Business Partner
Customers
Shipping
Define Goods Receiving Hours [OVSC]
Go to new entries and define and save it.
Contact persons tab page: - Enter the contact persons of the customer.
a. Company Code Data Screen: -
Account Management tab page: -
Reconciliation Account: - The Reconciliation account in General Ledger accounting is the account, which is, updated parallel to the sub ledger account for normal postings.
Payment Transactions tab page: -
Terms of Payment: - Specifies the key for defining payment terms composed of cash discount percentages and payment periods.
Defining terms of payment: -
SPRO
Sales and Distribution
Master Data
Business Partners
Customers
Billing Documents
Define terms of payment
Go to new entries and define and save it.
Payment History Record: - If we check this field the payment history of the customer will be recorded in his credit management.
To change the customer details go to xd02 and change the values and save it.
b. Sales Area Data Screen: -
Sales Tab Page: -
Sales District: - Specifies in which district the customer is there.
Before specifying the sales district we should define the sales district.
Defining Sales District: -
SPRO
Sales and Distribution
Master Data
Business Partners
Customers
Sales
Define sales district [OVR0]
Go to new entries and define and save it.
Customer Group: - Identifies a particular group of customers (for Ex: -wholesale or Retail) for the purpose of pricing or generating statistics.
Defining Customer Group: -
SPRO
Sales and Distribution
Master Data
Business Partners
Customers
Sales
Define customer groups [OVS9]
Go to new entries and define and save it.
Customer Pricing Procedure: - This field along with few other fields determines the pricing procedure that is given to a customer. [1]
Shipping Tab Page: -
Shipping Conditions: - This field along with few other fields determines the shipping point that is proposed by the system.
Defining Shipping Conditions: -
SPRO
Logistics Execution
Shipping
Basic shipping functions
Shipping point and goods receiving point determination scheduling
Define shipping conditions
Go to new entries and define and save it.
Delivering Plant: - Specifies the plant from which the goods should be delivered to the customer.
Order Combination: - If we want to combine multiple orders for the customer to create a single delivery we need to check this field.
Partial delivery per Item: - Specifies whether the customer requires full or partial delivery for the item.
Maximum partial delivery is 9.
Billing Documents Tab Page: -
Rebates: - If the customer wants to receive the rebates check this field.
If we check this field the customer can get rebates from the company.
Incoterms: - Incoterms specifies certain internationally recognised procedures that the shipper and the receiving party must follow for the shipping transaction to be successfully completed.
Account Assignment Group: - This field along with few other fields determines the General Ledger Account to which the sales values are to be posted.
Tax classification: - Specifies whether the customer is liable for tax or not.
Partner Functions Tab Page: -
Sold-to-Party (SP): - The customer who is placing order with the company.
Ship-to-Party (SH): - The customer who is receiving the goods.
Bill-to-Party (BP): - The customer on whom the bill is raised.
Payer (PY): - The customer who pays the bill.
Creating the Customer: -
Logistics
Sales and Distribution
Master Data
Business Partner
Customer
Create
XD01
Change
XD02
Display
XD03
Enter the Account Group [Here specify whether the customer is a SP, SH, BP or PY]
Enter the Account Group
Enter the Company Code
Enter the Sales Area
NOTE: - If we get the error sales area is not defined for the customers.
SPRO
Sales and Distribution
Master data
Define common distribution channels [VOR1]
And also go to
Define common divisions [VOR2]
Defining Account Groups: -
SPRO
Financial Accounting
Accounts Receivable and Accounts payable
Customer Accounts
Master Data / Records
Preparations for creating customer master data / record
Define account groups with screen layout (customer)
0001 Sold-to-party
Ship-to-party0002
Bill-to-party0003
0004 Payer
If the definition of the account group we can control the field status. We can make fields mandatory or optional or suppress or display mode.
Defining the number ranges for Account Groups: -
SPRO
Financial Accounting
Accounts Receivable and Accounts payable
Customer Accounts
Master Data / Records
Preparations for creating customer master data / record
Create number ranges for customer accounts [XDN1]
Go to change intervals
Select the button insert interval and define a number range.
NOTE: - If we check the field external for a number range it becomes an external assignment. Otherwise it becomes internal assignment.
Assigning the number ranges for Customer Account Groups: -
SPRO
Financial Accounting
Accounts Receivable and Accounts payable
Customer Accounts
Master Data / Records
Preparations for creating customer master data / record
Assign number ranges for customer account groups.
Assign the required number range to the account group.
Partner determination procedure: -
SPRO
Sales and Distribution
Basic Functions
Partner determination
Setup partner determination
Select setup partner determination for customer master
Step 1: -
Defining the Partner Functions: - Here we must not define any partner function.
Go to partner functions.
While defining the partner functions if we check the field Unique that partner faction has to be unique in the customer master i.e. we cannot have multiple partners of that function in a customer master.
Step 2: -
Assigning the partner functions to the Account group: -
Go to account groups function assignment.
Go to new entries and assign the required partner functions to the required account group and save it.
Step 3: -
Defining the partner determination procedure: -
Go to partner determination procedures
Go to new entries and define and save it
NOTE: - Procedure contains all the required partner functions.
Step 4: -
Placing the required partner functions in the procedure: - select the defined procedure and go to partner functions in procedure.
Go to new entries and place the partner functions
If we check the field Not Modifiable for a partner function it cannot change in the customer master.
If we check the field Mandatory Function it becomes a mandatory in the customer master and save it.
Step 5: -
Assigning the procedure to the Account Group: - Go to partner determination procedure assignment. Assign the procedure to the account group and save it.
2. Material Master Data: -
Logistics
Sales and Distribution
Master Data
Products
Material
Other Material
Create
MM01
Change
MM02
Display
MM03
Material master contains different views.
Enter the material number
Enter the industry sector
Enter the material type
Go to select views
Select the following views:
Basic Data 1
Basic Data 2
Sales Organisation Data 1
Sales Organisation Data 2
Sales General and plant data
Sales text
MRP 1
Accounting 1 and select organisational levels
Enter the plant
Enter the sales Organisation then distribution channel
Basic Data 1: -
Base unit of measure: - Specifies the unit of measure in which stocks of the material are managed.
Material Group: - Key that we use to group together several materials or services with the same attributes.
Defining Material Group: -
SPRO
Logistics General
Material Master
Setting for key fields
Define Material groups [OMSF]
Division: - Specifies in which division the material falls.
Gross Weight and Net Weight: - Specify the weight of the material.
Weight Unit: - Specifies the weight unit.
Sales Organisation Data 1: -
Base Unit of Measure: -
Sales Unit: - Here enter the unit of measure in which the material sold. We need to enter a value in this field if the sales unit differs from base unit of measure.
Note: - If the sales unit differs from the base unit we can maintain the conversion factors. To see that information go to additional data.
Delivering Plant: - Specifies the plant from which the material is delivered to the customer.
Cash Discount: - If we check this field we can give cash discounts for this material.
Tax classification: - Specifies whether the material is liable for tax or not.
Note: - To leave the tax both the customer and the material must be liable for tax.
Minimum Order quantity: - Specifies the minimum quantity in the base unit of measure that a customer may order for base material.
Minimum Delivery quantity: - Specifies the minimum quantity that can be delivered to the customer.
Rounding Profile: - Key that the system uses to adjust the order proposal quantity to the deliverable units.
Sales Organisation Data 2: -
Account assignment Group: - This field along with other fields determines the General Ledger Accounts to which different sales values are to be posted.
Item Category Group: - It determines the nature of the material we are defining.
Ex: -
Standard ItemNORM
Service or DeliveryLEIS
Third partyBANS Item
BOM ItemERLA/LUMF
PackagingVERP
Sales general / plant: -
Availability check: - Specifies whether and how the system checks the availability of the material and generating the requirement for the materials planning.
Batch Management: - Specifies whether the material is managed in Batches.
Transportation Group: - Grouping of the materials that share the same transportation requirement
Defining Transportation Group: -
SPRO
Logistics Execution
Shipping
Basic shipping functions
Routes
Route determination
Define transportation Group
Loading Group: - Grouping of the materials that share the same loading requirement.
Defining Loading Group: -
SPRO
Logistics Execution
Shipping
Basic Shipping Functions
Shipping point and Goods Receiving point determination scheduling
Define loading Group
MRP: - Material Requirement Planning
MRP 1: -
MRP Type: - Specifies how the requirement of the material can be planned.
Accounting 1: -
Valuation Class: -
Note: - Before creating the material master we should activate company code for material master.
Maintain Company codes for Material Management: -
SPRO
Logistics General
Material Master
Basic settings
Maintain company codes for material management [OMSY]
Define Storage Location: -
SPRO
Enterprise Structure
Definition
Materials Management
Maintain storage location [OX09]
Enter the plant number
Go to New entries
Extending the Organisational views for the Material Master: -
MM01-Create.
Enter the material, which you have already created.
Copy from material = material
Select the organisational views
Select the organisational levels
In the copy from fields enters the values in which the material has been already created.
In the fields on the left side of the screen enter the values to which we would like extend the material.
3. Customer Material Information Record: - We need to maintain this record then the customers are having their own names for the material rather the original names.
Note: - We need to enter the customer material number in the sales order on
the Ordering Party tab page, when we enter the customer material number in the sales order the system will automatically take the original material number.
Creating Customer Material Information Record: -
Logistics
Sales and Distribution
Master Data
Rebate Arrangements
Customer Material Information
VD51 Create.
Material Number: - In this field enter the original name of the material
Customer Material: - Here enter the material number by which the customer places order.
Creating Sales Order: -
Logistics
Sales and Distribution
Sales
Order
VA01 Create
Enter the order type OR & Enter the sales area.
Note: - To maintain the currency conversion rates use the transaction code
OC41.
4. Conditions Master Data: -
Condition Elements: -
a. Price
b. Discount or Surcharge
c. Tax
d. Freight
Ex: - for Condition Types: -
PricePR00
Material DiscountK004
Customer DiscountK007
CustomerK005 Material Discount
FreightKF00
Maintaining the values for these condition types is called condition records.
Maintaining the condition records for condition types is conditions master data.
Maintaining Condition Records: -
Logistics
Sales and Distribution
Master Data
Conditions
Selecting using condition type
VK11 create
Enter the condition type for which you are maintaining conditions Record.
Select the required key combination
In the material field enter the material for which we are maintaining the conditions record.
Enter the amount the system will automatically take currency and the calculation type.
Valid on and valid to: - The condition record is valid for those orders, which comes from the customer in the specified validity period.
Scales: - If we want to reduce or increase the amount as the quantity is increase select the condition record and go to scales.
Note: - Dont enter any value in the first line.
Setting upper limit and lower limit: - Select the condition record and go to details.
Note: - The price information in the sales order can be seen on the conditions tab page.
3. SALES DOCUMENT PROCESSING (SDP)
Structure of the Sales Document:
Header Data: - The general data that is valid for the entire document is recorded in the document header. For Ex: - Sold-to-party, Ship to party, Document date.
Item Data: - The data in the document header applies to all items in the document but same data applies only two specific items. This data is stored at item level.
Ex: - Material number, order quantity, ship to party, pricing, plant and
storage location.
Scheduling Line Data: - It gives the information about the delivery dates and the corresponding conformed quantities.
Note: - An item can have multiple schedule lines.
To see the header data in the sales document. Select the Icon Display Document Header Details or select Go to Header and select any tab page.
To see the Item data select Go to Item and select any tab page or double click on the item.
Note: - To Change the Ship to party at the item level select the partner
tab page and change it.
To see the schedule line data go to item data and select the tab page schedule lines.
Creating the Sales Documents with Reference:
Creating Quotation: -
Logistics
Sales and Distribution
Sales
Quotation
VA21 Create
Creating Order with reference to Quotation: -
Logistics
Sales and Distribution
Sales
Order
VA01 Create
Enter the order type OR and the sales area.
Select the button Create with Reference.
Specify the quotation number and say copy.
Document Flow: - When we create the documents with reference to some preceding documents it forms a document flow. In this flow if we know one document number with the help of Document Flow. We can know the remaining document numbers.
Note: - To See the remaining document numbers, go to the any sales
document in the flow and select the icon Display document flow.
Note: - If we get the error the order type is not defined for sales area.
SPRO
Sales and Distribution
Sales
Sales documents
Sales documents header
Assign sales area to sales document types
Sales Document Types: -
SPRO
Sales and Distribution
Sales
Sales Document
Sales Document Header
Define Sales Document type [VOV8]
Ex: -
IN Inquiry
QuotationQT
OrderOR
Returns sales documentsRE
CS Cash Sale
Rush OrderRO
Scheduling AgreementDS
Functionality of the sales document type: -
Sales Document Category: - Its a classification for the different types of documents that we can process in the sales and distribution system
Ex: -
InquiryA
QuotationB
C Order
Sales Document Block: - Determines whether the sales document is blocked for use. If we block a sales document type users cannot create new sales documents of this type.
Number range internal assignment and Number range external assignment: - Number that determines how the documents are to the numbered by the system. It indicates which number range is relevant for document type.
Creating Number ranges for sales Documents: -
SPRO
Sales and Distribution
Sales
Sales Documents
Sales Document header
Define number ranges for sales documents [VN01]
Item Number Increment: - Specifies the increment by which you want the item numbers in the sales document to increase when the system automatically generates the item number.
Sub Item Increment: - This is for sub items.
Reference Mandatory: - Indicates whether a reference document is mandatory when we create a sales document. If so the indicator also specifies which type of reference document we should use.
Item Division: - If we check this field the division at the item level is proposed from the material master record of the item otherwise the division we enter in the sales document header also counts for all the items.
Check Division: - Controls how the system reacts during the sales order processing when the division at the item level differs from the division in the document header.
Read Info Record: - Determines whether the system read the customer material information record for the sales document type.
Check Credit Limit: - Specifies whether the system runs credit checks and how it response to the check during the sales order processing.
Check purchase order number: - Specifies whether the system should check if the purchase order number entered is already existing for other sales document.
Screen Sequence Group: - Controls which screen we see during a particular transaction and in which sequence they appear.
Transaction Group: - Its a grouping that allows you to control certain characteristics of a transaction according to sales document type.
Document Pricing Procedure: - This field along with few other fields determines the pricing procedure that is proposed by the system.
Display Range: - Specifies whether the system displays only main items or sub items or all the items in the sales document.
F code for over view screen: - Determines which overview screen we reach during the sales order processing after we enter the data in the initial sales document screen.
Quotation Messages: - Set an indicator here if you want to receive a message informing you that open quotations exist when we create a sales document. Depending on the indicator we select the system searches for open quotations in the sales document either at the header level for the customer or item level for the material.
Outline agreement messages: - This is for agreements.
Incomplete Messages: - Specifies whether an incomplete document can be saved. If we check this field we cannot save the incomplete document until we enter the missing data.
Delivery type: - specifies the corresponding delivery document type for the sales document.
Outbound delivery with reference toEx: - LF order.
Delivery Block: - Indicates it the entire sales document is blocked for delivery.
Shipping Conditions: - If we specify the shipping condition here the value from the customer master record is over return by this value.
BILLING: -
Delivery related billing type and order related Billing type: - Specifies the corresponding billing document types.
Ex: - InvoiceF2
Billing Block: - Indicates whether the item is blocked for billing or not.
Propose Delivery Date: - If we check this field the system automatically proposes the current date as the delivery date.
Lead-time in days: - Specifies the number of days after the current date that the sales document uses for the proposal of the requested delivery date.
Propose P O Date: - If we check this field the system automatically proposes the current date as the purchase order date.
Contract Data allowed: - This field controls whether we can enter the contract data for the sales document type.
Item Categories: -
InquiryAFN
AGN Quotation Standard Item
Sales OrderTAN
INAFNN
QT FreeAGNN of charge Item
ORTANN
Third Party ItemTAS
Defining Item Categories: -
SPRO
Sales and Distribution
Sales
Sales Documents
Sales Document item
Define item categories
Functionality of the Item Categories: -
Billing Relevance: - Specifies the reference document to create the billing document.
Pricing: - Specifies whether an item is relevant for pricing or not
Business item: - If we check this field during the sales order processing the business data that we enter an item is allowed to differ from the business data in the header.
Schedule Line allowed: - Indicates whether we can create schedule lines for the item.
Item relevant for delivery: - Indicates whether a text item is relevant for delivery processing.
Note: - We need to check this field in the item category TATX. Which is
for text items.
Returns: - If we check this field it becomes a returns item.
Note: - We need to check this field in the item category REN. Which is
for returns.
Weight / Volume Relevant: - Indicator that controls whether the system calculates weight and volume for the item in the sales document.
Credit Active: - Indicates whether the credit management functions are active for the document items.
Determine Cost: - Indicates whether the system determines the cost of a sales document item during pricing.
Note: - The cost condition type is VPRS.
Automatic Batch Determination: - If we want to use automatic batch determination for materials handled in the batch active this field.
Rounding Permitted: - Indicates whether rounding is permitted or not.
Note: - Depending on the rounding profile specified in the material master the order quantity can be rounded in the sales order.
Order Quantity = 1: - If we check this field the order quantity for each line item is limited to one.
Item Category Determination: -
SPRO
Sales and Distribution
Sales
Sales Documents
Sales Document Item
Assign Item Categories
We have to assign the item category to the combination of
Sales Document type
Item category group
Usage
Higher lever item category
Schedule line categories: -
Defining Schedule line categories: -
SPRO
Sales and Distribution
Sales
Sales Documents
Schedule Lines
Define schedule line categories [VOV6]
CS Third party item
Inquiry schedule lineAT
Sales orderCP, CV, CN schedule lines
QuotationBN
Functionality of a Schedule Line Category: -
Movement type: - Specifies the physical or logical movement of materials leading to a change in the stock levels or resulting in the consumption of the material.
Goods Issue Delivery601
602 Returns
Posting the stock in the plant561
Plant to plant stock301 transfer
Return of the stock transfer302
Item relevant for Delivery: - Indicates whether the item that is related to a schedule line is relevant for delivery or not.
Order type: - Specifies the order type NB purchase requisition.
Note: - We need to specify, NB in this field for the schedule line category CS which is used for third party item.
Requirement/Assembly: - If we check this field the transfer of requirements will take place into the inventory management for a better planning of material requirement.
Availability: - Specifies whether the system should check the availability of the material.
Schedule line category determination: -
SPRO
Sales and Distribution
Sales
Sales Documents
Schedule Lines
Assign schedule line categories
We need to assign the schedule line category to the combination of Item category and MRP Type.
NORMItem category group
Sales Document
IN
AFN
+MRP Type
AT Item Relevant Delivery
QT
AGN
+MRP Type
BN Item Relevant Delivery
OR
TAN
+MRP Type
CP Item Relevant Delivery
4. PRICING (PG)
This concept is based on condition technique.
Its the combination of:
1) Condition Tables
2) Access Sequence
3) Condition Types
4) Pricing Procedure
1. Condition Tables: - Condition table contain the key fields for maintaining condition records. I.e. in other words condition records are stored in condition table.
Note: - A condition type can have multiple condition tables.
Note: - A condition table can be used for multiple condition types.
Defining condition tables: -
SPRO
Sales and Distribution
Basic functions
Pricing
Pricing control
Define condition tables [V/03]
Create condition tables
Enter a table number beyond 600
From the field catalogue, which is there on the right side of the screen select the required key fields.
To get the valid on / valid to fields while maintaining the condition records we need to check the field with validity period.
Go to icon Technical View
The fields which are marked, as footer field appears at the footer level at the condition records and the remaining fields appears at the key level.
Select the Icon Generate for generating the condition table.
To save the condition table, select the button Local object.
2. Access Sequence: - Access sequence is a search strategy with the help of which the system gets the valid condition records. It contains the required condition tables in the required order.
Note: - If required an access sequence can be used or assigned to multiple
Condition types.
Note: - The order in which the condition table are placed in access sequence
is important generally it is most specific to most generic
Defining Access Sequence: -
SPRO
Sales and distribution
Basic functions
Pricing
Pricing control
Define access sequences
Maintain access sequences
Go to new entries and define the access sequence.
Select the defined access sequence and go to accesses.
Go to new entries and place the condition tables in the required order
While placing the condition tables check the field exclusive. By doing so if the system finds a valid condition record in the first condition table it will not go to the next condition table
Select the condition table and go to fields the system gives the warning message the field assignment has not yet been made say enter till we get the fields.
Repeat the same step for all the condition tables and save it.
Note: - After defining the access sequence assign it to the corresponding condition type.
3. Condition Types: -
Defining condition types: -
SPRO
Sales and Distribution
Basic functions
Pricing
Pricing control
Define condition types.
Maintain condition types.
Functionality of a condition type: -
Access Sequence: - In this field specify the corresponding access sequence for the condition type.
Condition class: - It is the preliminary structuring of condition types.
Ex: - Surcharges or discounts and price
Plus/Minus: - If we specify negative here a condition type becomes discount and if we specify positive it becomes surcharge.
Calculation type: - Determines how the system calculates price discounts and surcharges in a condition type.
For Ex: - the system can calculate a price as a fixed amount or as a percentage based on the quantity, weight, or volume.
Condition Category: - Its a classification of conditions according to pre-defined categories.
Rounding Rule: - The rule that determines how the system rounds of condition values during pricing.
Manual Entries: - Indicator which controls the priority with in a condition type between a condition enter manually and a condition automatically determined by the system.
Amount / Percent: - If we check this field the amount / percentage of a condition type can be change during the document processing.
Quantity Relation: - Specifies whether the conversion factors for the units of measure in the condition type can be change during document processing.
Delete: - If we check this field the condition type can be deleted during the sales document processing.
Value: - If we check this field the condition value can be changed during the document processing.
Calculation type: - If we check this field the calculation type can be change during the document processing.
Item condition: - If we check this field for a condition types it becomes item condition, which has to be enter at the item level only.
Header condition: - If we check this field for a condition type it becomes header condition, which has to be entered at the header level only
Ex: - RB00 (Discount).
Note: - After entering the header condition type click on the button activate.
Note: - The condition amount of the header condition is copied as it is to all the line items in the document
Group condition: - If we check a header condition as a group condition the condition amount is distributed proportionately among all the line items in the sales document.
Valid from & valid to: - specifies the beginning and ending of the validity date that the system automatically proposes when we create condition records for the condition types.
Scale Basis: - Determines how the system interprets a pricing scale in a condition, for Ex: - the scale can be based on quantity weight and volume.
Check value: - Indicates whether the sale rates must be entered in ascending or descending order.
Note: - Header condition wont be having access sequence.
4. Pricing Procedure: - Pricing procedure contains all the required condition types in the required order.

How to Learn HR module online

Hi all
Iam learning SAP ABAP now.Besides that if we have another functional module basic knowledge,i think it will be added advantage.How complex learning HR module at home pc? I want to know just basics.Is HR possible or any other module like BW...?Advise me.
Thanks

hi,
use SDN and help.sap.com also
Please refer to http://www.sapbrainsonline.com/TUTORIALS/FUNCTIONAL/HR_tutorial.html
There are lots of PDFs available on this site which you can read and learn more.
Reward points ....
Regards,
Rahul

Learning Other Modules

Hi all,
I am a SD Certified consultant working in production support.
I would like to learn other modules and give certification in that.My current project is such that I can learn Transportation and a part of warehouse management.
Can I give certification in LE & WM.If so how will be the scope for SD with LE & WM
If not which module can i choose? How is the scope for SD with CRM or SD with IS - Retail
I need your valuable suggestions
Regards
Mano

Hi Mano
Though i donnot recommend to discuss these type of things in this forum i wabt to tell you some facts.
Please try first to understand ur project and the industry very well.SD is such a big thing most of the consultants get goofed up in framing a proper solution in real time.I strongly recommend you to conentrate on project and what is required for it and try to get indepth knowledge of SD and its integration with core modules like Fi and MM
Ultimately its the client satisfaction that matters so supercede the client expectations.
Happy consulting !

Plz provide tutorial to learn the Module pool programing?

Hello,
Please provide me with the Tutorials which will be helpful to learn Module Pool Programming.
If any one can provide me with the screen shots then it would be great!
ANy help would be appreciated......
Thank You!
Krishna Chaitanya

Hi,
Screens are the most general type of user dialog that you can use in ABAP programs. You do not define them in ABAP programs, but instead in the Screen Painter. A screen consists of the input/output mask and the flow logic. You can define screens for any program with type 1, M, or F.
The screens in a single ABAP program can be combined to form screen sequences. You can call single screens or screen sequences either using a transaction code from outside the ABAP program, or by using the CALL SCREEN statement in the corresponding ABAP program. When you call a screen or screen sequence, the screen flow logic takes control of the ABAP program execution. You can define screen sequences dynamically by setting the next screen attribute for a screen dynamically in the ABAP program.
A screen consists of the input/output mask and the flow logic. The screen flow logic is divided into the Process Before Output (PBO) event, which is processed before the screen is displayed, and the Process After Input (PAI) event, which is processed after a user action on the screen.
The following diagram shows the place of screens between the GUI status and the ABAP program:
The screen flow logic calls dialog modules in the ABAP program, either to prepare the screen for display (PBO event) or to process the user's entries (PAI event). Screens are dynamic programs, and have their own data objects, called screen fields. These are linked to the input/output fields that appear on the screen itself. When the screen is displayed, and when it finishes processing, the system passes data between the screen fields and data objects in the ABAP program. Data is copied between identically-named fields.
Each screen has a GUI status, containing a menu bar, standard toolbar, and an application toolbar. Like screens, GUI statuses are independent components of the ABAP program. You create them in the ABAP Workbench using the Menu Painter. You assign GUI statuses to screens dynamically in your ABAP programs. Each screen is linked to the current GUI status by a special screen field into which the corresponding function code is placed whenever the user chooses a function. The screen passes the function code to the ABAP program just like any other screen field. You can then read it in the program.
Screen Attributes
Like all objects in the R/3 Repository, screens have attributes that both describe them and determine how they behave at runtime. Important screen attributes for ABAP programming:
Program
The name of the ABAP program (type 1, M, or F) to which the screen belongs.
Screen number
A four-digit number, unique within the ABAP program, that identifies the screen within the program. If your program contains selection screens, remember that selection screens and Screen Painter screens use the same namespace. For example, if you have a program with a standard selection screen, you may not contain any further screens with the number 1000. Lists, on the other hand, have their own namespace.
Screen type
A normal screen occupies a whole GUI window. Modal dialog boxes only cover a part of a GUI window. Their interface elements are also arranged differently. Selection screens are generated automatically from the definition in the ABAP program. You may not define them using the Screen Painter. A subscreen is a screen that you can display in a subscreen area on a different screen in the same ABAP program.
Next screen
Statically-defined screen number, specifying the next screen in the sequence. If you enter zero or leave the field blank, you define the current screen as the last in the chain. If the next screen is the same as the current screen, the screen will keep on calling itself. You can override the statically-defined next screen in the ABAP program.
Cursor position
Static definition of the screen element on which the cursor is positioned when the screen is displayed. By default, the cursor appears on the first input field. You can overwrite the static cursor position dynamically in your ABAP program.
Screen group
Four-character ID, placed in the system field SY-DYNGR while the screen is being processed. This allows you to assign several screens to a common screen group. You can use this, for example, to modify all of the screens in the group in a uniform way. Screen groups are stored in table TFAWT.
Hold data
If the user calls the screen more than once during a terminal session, he or she can retain changed data as default values by choosing System ® User profile ® Hold data.
Screen Attributes
Like all objects in the R/3 Repository, screens have attributes that both describe them and determine how they behave at runtime. Important screen attributes for ABAP programming:
Program
The name of the ABAP program (type 1, M, or F) to which the screen belongs.
Screen number
A four-digit number, unique within the ABAP program, that identifies the screen within the program. If your program contains selection screens, remember that selection screens and Screen Painter screens use the same namespace. For example, if you have a program with a standard selection screen, you may not contain any further screens with the number 1000. Lists, on the other hand, have their own namespace.
Screen type
A normal screen occupies a whole GUI window. Modal dialog boxes only cover a part of a GUI window. Their interface elements are also arranged differently. Selection screens are generated automatically from the definition in the ABAP program. You may not define them using the Screen Painter. A subscreen is a screen that you can display in a subscreen area on a different screen in the same ABAP program.
Next screen
Statically-defined screen number, specifying the next screen in the sequence. If you enter zero or leave the field blank, you define the current screen as the last in the chain. If the next screen is the same as the current screen, the screen will keep on calling itself. You can override the statically-defined next screen in the ABAP program.
Cursor position
Static definition of the screen element on which the cursor is positioned when the screen is displayed. By default, the cursor appears on the first input field. You can overwrite the static cursor position dynamically in your ABAP program.
Screen group
Four-character ID, placed in the system field SY-DYNGR while the screen is being processed. This allows you to assign several screens to a common screen group. You can use this, for example, to modify all of the screens in the group in a uniform way. Screen groups are stored in table TFAWT.
Hold data
If the user calls the screen more than once during a terminal session, he or she can retain changed data as default values by choosing System ® User profile ® Hold data.
Check the below link:
http://sap.mis.cmich.edu/sap-abap/abap09/index.htm
http://wiki.ittoolbox.com/index.php/FAQ:What_is_module_pool_program_in_abap%3F
http://help.sap.com/saphelp_46c/helpdata/en/35/26b1aaafab52b9e10000009b38f974/content.htm
http://sap.mis.cmich.edu/sap-abap/abap09/sld011.htm
http://sap.mis.cmich.edu/sap-abap/abap09/index.htm
You can also check the transaction ABAPDOCU which gives you lot of sample programs.
Regards
Kiran Sure

HOW TO LEARN QM MODULE

respected all
I would like to know the qm module deeply . can anybody guide me from where i should start??????//
thanks
abhay

Hi,
Before learn about configuration and end user part in the QM .
Try to learn the the concept of QM and how it was mapped in Sap
You can use the book " Quality managament with sap " which is available in Sap press
it have the both the real end explain about the quality and the systems which is used in sap
and the configuration parts.
check the link for more :
New in QM

Differences between R12 and 11.5.9 in Oracle Learning Management Module

Hi,
I am into One Upgrade Project.
I would like to know what are the differences between R12 and 11.5.9 in Oracle Learning Management and need to know any new Tables, Views, Forms and Reports got upgraded?.
Thanks & Regards,
Srinivasulu Vakati

Hi Anders,
Could you please explain me what is this SWAN Interface ?
Kind Regards,
Naga Suresh. Challapalli (Naga)

IS that SAP SD have market... any one kindly suggest whether i need to learn this module or not?

Hi Guys..
I Did my MBA in Tourism and Hospitality and i have an 3 years exp in Travel field... now i want to change my field for that reason i am willing to learn SAP but i have an confusion to learn which course.
i approached one institute regarding the same they suggested to go with SAP SD...and also which Institute is Good for learning SAP...
one of my friend suggested to join at Vayuputhra Communications Ltd
Kindly advice....

If you access the Crucial website, they have a program that will scan your MBP and let you know the RAM options that you have.
Best places to order RAM is Crucial and OWC.
Ciao.

What are the softwares that I need to learn Oracle Apps- Financial module?

Hi All,
I'm a PL/SQL developer and supposed to learn Oracle Apps - Financial Module from Technical perspective as a part of my new job requirement. So, could you please help me figure out the softwares required to start learning Oracle Apps. ?
I think, I need servers and clients of E-Business Suite & RDBMS (10 g or 11g). I'm afraid whether 200GB of free disk- space & 3 GB RAM on my Desktop may not be sufficient if I install both servers & Clients.
So, please suggest the essential components of E-business Suite and RDBMS I should get to start learning Financial Module considering the above limitation.
All suggestions are welcomed!
Regards,
MK

Hi Mk;
I'm a PL/SQL developer and supposed to learn Oracle Apps - Financial Module from Technical perspective as a part of my new job requirement. So, could you please help me figure out the softwares required to start learning Oracle Apps. ?You need to E-Business Suite r11 or r12 version
I think, I need servers and clients of E-Business Suite & RDBMS (10 g or 11g). I'm afraid whether 200GB of free disk- space & 3 GB RAM on my Desktop may not be sufficient if I install both servers & Clients.
So, please suggest the essential components of E-business Suite and RDBMS I should get to start learning Financial Module considering the above limitation.When u make EBS installation(DEMO which comes wiht data), db will be create automaticly. For You can make installation on external disk wiht VMware option. For installation steps-installlation files-stage,require disk size etc.. check my blog
http://heliosguneserol.wordpress.com/category/step-by-step-oracle-e-business-suite-installation/
There is also DEMO instance avaliable on below link
www.solutionbeacon.com
Regard
Helios

Need suggestions to learn Oracle Apps Technical Modules

Hi All,
I have done my Bachelors in Computers and Am OCP Certified in Oracle9i ( development). I am having 4.5 Years of experience as a Oracle PL/SQL Developer ( Not completely into Development but am into maximum Application support and some part of Development. Now I want to learn Oracle Apps Technical. But am not aware of the Modules which are helpful to my career. I worked for many domains like Retail, Pharma, Manufacturing and Telecom.
So please have a look into this and suggest me the Module details. So very soon am planning to learn those Modules which are like hot cake in Market.
Many thanks in advance.

I have done my Bachelors in Computers and Am OCP Certified in Oracle9i ( development). I am having 4.5 Years of experience as a Oracle PL/SQL Developer ( Not completely into Development but am into maximum Application support and some part of Development. Now I want to learn Oracle Apps Technical. But am not aware of the Modules which are helpful to my career. I worked for many domains like Retail, Pharma, Manufacturing and Telecom.
So please have a look into this and suggest me the Module details. So very soon am planning to learn those Modules which are like hot cake in Market.This topic was discussed many times in the forum before, please see old threads for details.
https://forums.oracle.com/forums/search.jspa?threadID=&q=Apps+AND+Developer&objID=c3&dateRange=all&userID=&numResults=15&rankBy=10001
https://forums.oracle.com/forums/search.jspa?threadID=&q=Technical+AND+Consultant&objID=c3&dateRange=all&userID=&numResults=15&rankBy=10001
https://forums.oracle.com/forums/search.jspa?threadID=&q=Functional+AND+Consultant&objID=c3&dateRange=all&userID=&numResults=15&rankBy=10001
Thanks,
Hussein

Is CO module is too difficult to learn in ECC6?

Hi folks,
I am currently doing my part time MBA & i am interested to learn FI/CO module.
Some people say that it's very very difficult to learn CO module
as it's quite extensive in ECC6.Only charted accounts or good experienced FI consultants can go for CO module.
i need to take decision wheather to go for FI/CO module or not.
i am waiting for ur better suggestion.
Thanks
pabi

Hi Pabi,
If you are doing your specialization in Finance then you will have two papers, Management accounting and Company accounts. If you are well versed in these there should not be any problem. All I need to say is keep your fundamentals clear. It's all the same for CAs as well.
Regards,
Abhisek

Enterprise learning/ Learning solution

Hi all,
I am looking for business requirements for the learning solution module.
Can anyone share some thoughts and requirements of the same!
Regards,
Bharat

Not sure I have got it completely wrong last 18 years, but shouldn't the requirements come from the customer? Obviously with help from annexperienced consultant to refine and discuss them, but if a customer needs a set of requirements from outside, then there's a perfectly cheap solution: they have no real business need and therefore don't need an LSO. Happy days :-)

Approver Invoice history (AP Module)

Hello All,
I am a beginner to EBS and currently learning AP module.
I have a quick question and hoping to get some assistance
The question is,
Is there any "find" function in AP module where an approver could see one year old approved invoices??
I have an understanding that approver can see all the notifications under the notification list, but I was looking if there is any functionality in the AP module where the approver could see the history of approved invoices since one year
Thanks in advance!
Best KK

Hi
Thanks for the reply...Iam aware that approver will be able to see all the invoices under approvers notification List...since we run concurrent program called Purge Obsolete Workflow Runtime Data which is normally scheduled for 7-14 days this program deletes the invoices under approvers notification list which are older than 7 or 14 days as per scheduled..
Now my question
Is it possible to increase the number of days lets say for one year to run the concurrent program Purge Obsolete Workflow Runtime Data?
will the performane be affected if we increase the number of days?
Approvers can query invoices through AP Inquiry but the problem is the company doesn't want to give access for AP Inquiry to the approvers because of some security reasons.
Is their any other way to see the invoices by the approvers?

Definition of Terms on Adobe Learning Dashboard

What is the difference between a learner status of "In Progress" and "Incomplete?"
What causes a learner to be defined as "Needs Intervention?"
In my experience/test run, a learner who is in the process of taking the course (actively has it loaded and is going through) is concurrently defined as "Incomplete" and "Needs Intervention" which seems odd to me, since that learner just launched the course and is in the process of taking it.
Thanks for any insights!

These are 2 different aspects,
learner status as "In Progress" and "Incomplete" is shown module wise
and "In Progress" and "Needs Intervention" is shown as per status of full course
Please find the details of both below:
Following is difference between "In Progress" and "Incomplete": (in reference with Students ->Group Graph)
- If the user takes the module before Delay date and has not completed it yet - User will fall in "In Progress" group
- If the learner visits module after delay date and the module does not complete the module he will fall in "Incomplete" group
- If learner never visits the module after delay date he will remain in "In Progress" group
Need Inetrvention criteria is set while creating the course by switching on/off the options of "Low Participation" "Quiz Fail" and "Incomplete"
Following is difference between "In Progress" and "Needs Intervention": (in reference with Overview -> Student Progress Graph)
- All students who have not completed the course before Needs Intervention date are in "In Progress" group
- All students who did not complete atleast one module before Needs Intervention date but visits any module of the course after Needs Intervention date are moved to "Needs Intervention" group
- All students who did not complete atleast one module before Needs Intervention date and does not visit any module of the course after Needs Intervention date remain in "In Progress" group
I hope this answer clears the query!
Message was edited by: Anamika_G

Learning SD Module

Similar Messages

Maybe you are looking for