SAP-SD

EDI

2008-03-19T23:42:00.000-07:00

EDI is nothing but Electronic data interchange.SAP will support EDI through
Intermediate documents(IDOCS).

For creating sales documents(sales order) through IDOCS you will have to use the
T code WE19.In that click basic type and enter order05(IDOC type) and select via
message type then enter ORDERS(message type), click execute.

you will get to see many fields.here you have to enter the datas that you
enter in the VA01 screen in order to create sales order.The datas such as
material name,date,qty,P.O no etc.. after entering all the datas you click
standard inbound the IDOC would be created by the system.You can see the created
order by going in to VA03 screen.

NExt time when you create the IDOC, in same WE19 screen click existing IDOC
and enter the IDOC which you created in the above step and just change the P.O
no.Sytem will create new sales order through new IDOC

Before doing all you need to maintain the partner profile in T code WE20.For
this Discuss with EDI consultant.

2008-02-07T12:48:00.000-08:00

>>Previous>>

Standard settings

Company code 0001 has already been created in clients 000 and 001 for the country DE (Germany). All country-specific information ("parameters") is preset in this company code, such as the payment methods, tax calculation procedures, and chart of accounts typical for this country.

If you want to create a company code for the USA and its legal requirements, you must first of all run the country installation program in client 001.

The country of company code 0001 is then set to "US" and all country-specific parameters related to it are set to the USA. For more information, see the Set Up Clients activity under "Basic Functions" in the Customizing menu.

Recommendation

You should keep the preset company code number 0001 if you only require one company code. This keeps to a minimum the number of tables you need to set up.

You can copy a company code using a special Customizing function. Company code-specific specifications are copied to your new company code. The target company code must not yet be defined, it is defined automatically during the copying procedure.

SAP recommends the following procedure when creating company codes:

1. Create the company code using the function "Copy Company Code".

2. Enter special company code data with the function "Edit Company Code Data".

You can also use the function "Edit Company Code Data" to create a company code. However, in this instance, the company code "global data" is not copied. If you create a company code using the "Copy" function, most of the "global data" is also copied.

Further notes

You should create a company code according to tax law, commercial law, and other financial accounting criteria. As a rule, a company code in the SAP system represents a legally independent company. The company code can also represent a legally dependent operating unit based abroad if there are external reporting requirements for this operating unit, which can also be in the relevant local currency.

For segment reporting according to Anglo-American accounting practices, you need to represent the regions in which the company has significant dealings. This reporting data can be generated entirely on the basis of company codes.

For processing company codes, there are extended functions that you can access with the function call "administer" or "Copy, delete, check company code". The entry in the company code table is processed in these functions as well as all dependent Customizing and system tables in which the plant is a key.

For more information on the extended functions, see Copy/Delete/Check/Process Project IMG.

In addition to these functions, there is also the "Replace" function. You use this function if you want to change a company code key. This is only possible if no postings have been made in the company code that is to be replaced. You should therefore only use this function for newly-created company codes.

Activities

1. Create your company codes based on the reference (company code 0001) delivered with the standard system. SAP recommends using the function "Copy Company Code" to create your company codes.

2. Go to the activity "Edit Company Code Data" and change the name, description, address, and currency. Maintain the company code data that has not been copied.

3. Use the project IMG view to postprocess data that is changed automatically. You can also carry out postprocessing at a later stage since the system keeps the generated project view.

Maintain Controlling Area

In this IMG activity you

create new controlling areas or
Copy existing ones.

The controlling area is an organizational unit in Accounting used to subdivide the business organization from a cost accounting standpoint.

The controlling area is embedded in the organizational structure as follows:

A controlling area may be assigned one or more company codes.

1:1 relationship

You carry out cost accounting on a cross-company code basis.

The internal and external accounting viewpoints are identical.

1:n relationship

In cross-company-code cost accounting, all data relevant to cost accounting appears in a common controlling area and is available for allocations and evaluations. The internal and external accounting goals diverge. This method is preferred when, for example, a corporation posesses several independent subsidiaries and undertakes centralized cost accounting for all.

If you implement the CO (Controlling) component, you must maintain basic data and control indicators in the for the controlling area. You make these settings in the Controlling IMG.

Recommendation

We recommend that you use the controlling area "0001" supplied by SAP "0001" or that you copy this controlling area to your own controlling area and then making adjustments to suit your needs. Preliminary settings such as the definition of number ranges are already maintained for this controlling area.

Activities

Copy Controlling Area "0001"

1. Adapt the default settings to your country.

a) To do this, choose Enterprise Structure -> Country-Specific Settings in Customizing.

b) Choose Change Country-Specific Settings and Country version.

2. Create your own controlling area with company code as a Copy of controlling area "0001" with company code "0001".

3. Adjust this copy to your requirements.

a) To do so, in the dialog box, choose Maintain controlling area.

b) Select your controlling area and change the settings.

Create Controlling Area

1. Choose Maintain controlling area

2. Choose New entries and enter the basic data.

3. Enter a key and a name for your company code.

4. Specify the allocation of company codes and controlling area.

5. Make the currency settings.

6. Speciy a chart of accounts for the controlling area.

7. Enter a fiscal year variant.

Delete controlling area

You can delete the controlling areas supplied by SAP if you:

Create all organizational units afresh.
Have created all organizational units using the SAP delivery data.

To do so, create your own controlling area with company code as a copy of the controlling area "0001" with company code "0001".

Now delete the controlling areas you no longer require.

To delete a controlling area supplied by SAP, proceed as follows:

1. In the dialog box, choose Delete SAP Delivery Data.
2. From the list, select the controlling areas you want to delete.
3. Choose Delete.

Note on deleting SAP delivery data

Further Notes

In cross-company code cost accounting, where a controlling area includes several company codes with differing currencies, assign the group currency as controlling area currency. The related company codes must all use the same operative chart of accounts .

During number assignment for organizational units in the controlling area ( cost center, profit center, etc.), keep the possible addition of other company codes in mind as you work.

All internal allocation transactions refer only to objects belonging to the same controlling area.

>>>Next>>>

2008-02-07T12:26:00.000-08:00

>>previous>>

Enterprise Structure

In this section, you will learn how to portray the specific organizational structure of your business in the R/3 System.

To help you portray your company structure, different Accounting, Logistics and Human Resources organization units are provided.

First analyze the structures and procedures in your company, and then match them to the SAP structures. There are various organization elements defined as examples in the standard version. Normally these would not cover all your needs. Extend the elements as required.

During the clarification stage, work with the structures delivered by SAP. In order to obtain a high degree of indentification and acceptance from project members and user departments from the start, you may have to change some of SAP's terminology.

You should limit the number of persons authorized to maintain organization elements. Define the authorization profiles accordingly. As soon as your organization units are ready, access should be locked so that no other changes can be made.

Note

The definition of organization units is a fundamental step in your project. It is a critical factor in how the project will be structured.

You should not use more organization units than necessary. Only use new organization units if this is required by the existing data structures.

Once you have decided on an organizational structure it is not easy to change it.

Define company

In this step you can create companies. A company is an organizational unit in Accounting which represents a business organization according to the requirements of commercial law in a particular country.

You store basic data for each company in company definition. You only specify particular functions when you
customize in Financial Accounting. Company G0000 is preset in all foreign key tables.

In the SAP system, consolidation functions in financial accounting are based on companies. A company can comprise one or more company codes.

When you create a company you should bear in mind the following points relating to group accounting:

If your organization uses several clients, the companies which only appear as group-internal business partners, and are not operational in each system, must be maintained in each client. This is a precondition for the account assignment of a group-internal trading partner.
Companies must be cataloged in a list of company IDs which is consistent across the group. The parent company usually provides this list of company IDs.
It is also acceptable to designate legally dependent branches 'companies' and join them together as a legal unit by consolidation.

Recommendation

SAP recommends that you keep the preset company ID G00000 if you only require one company. In this way you reduce the number of tables which you need to adjust.

Activities

Create your companies.

Further notes

All company codes for a company must work with the same operational chart of accounts and fiscal year. The currencies used can be different.

Edit, Copy, Delete, Check Company Code

In this activity you create your company codes. The company code is an organizational unit used in accounting. It is used to structure the business organization from a financial accounting perspective.

We recommend that you copy a company code from an existing company code. This has the advantage that you also copy the existing company code-specific parameters. If necessary, you can then change certain data in the relevant application. This is much less time-consuming than creating a new company code. See "Recommendations" for more details about copying a company code.

If you do not wish to copy an existing company code, you can create a new company code and make all the settings yourself. You define your company codes by specifying the following information:

Company code key

You can select a four-character alpha-numeric key as the company code key. This key identifies the company code and must be entered when

posting business transactions or creating company code-specific master data, for example.

Company code name

Address data

The address data is necessary for correspondence and is printed on reports, such as the advance return for tax on sales/purchases.

Country currency

Your accounts must be managed in the national currency. This currency is also known as the local currency or the company code currency.

Amounts that are posted in foreign currency are translated into local currency.

Country key

The country key specifies which country is to be seen as the home country; all other countries are interpreted as "abroad". This is significant for

business and payment transactions because different forms are used for foreign payment transactions. This setting also enables you to use

different address formatting for foreign correspondence.

Language key
The system uses the language key to determine text automatically in the language of the relevant country. This is necessary when creating checks, for example.

You can set up several company codes per client to manage the accounts of independent organizations simultaneously. At least one company code must be set up in each client.

To take full advantage of SAP system integration, you must link company codes to the organizational units of other applications. If, for example, you specify a CO account assignment (for example, cost center or internal order) when entering a document in FI, then the system must determine a controlling area to transfer this data to CO. You must specify how the system is to determine the appropriate controlling area.

The system derives the controlling area from the company code if you assign it directly to a company code. You can also assign several company codes to one controlling area.

>>>Next>>>

Sales and Distribution Process Online Learning

2008-02-04T04:53:00.000-08:00

>>Previous>>

Enter picked materials on delivery document

From the SAP Easy Access Menu: Logistics -> Sales and distribution -> Shipping and transportation-> Outbound delivery-> Change -> Single document

Enter your delivery document number from the previous exercise, and click the enter button. On the Outbound delivery screen, click on the picking tab. Notice that the BC-S line lists the storage location (SLoc) as 30. Also note that the box under Pick quantity is blank. This is because the quantity loaded onto the trucks has not yet been entered. Now look at the OvrllPickStatus (Overall Pick Status) and note that shows that the order has not yet been picked. Enter 20 in the box under Pick quantity, and click the enter button. Now look at the OvrllPickStatus, and confirm that it shows that the order has been fully picked. The order is now ready to be sent to Southwest Recreational Vehicles.

The last task for Clara is to update the inventory of S Beach Cruisers at SOS. This process is called posting of goods issue. Click save to record the picked quantity. You should be taken back to the initial Change Outbound Delivery screen. If your delivery document number is not already shown in the Outbound delivery box, enter it now. Now click the Post goods issue button near the top of the screen. A message telling you that your outbound delivery has been saved should flash across the bottom of the screen.

To confirm that the correct amount of Beach Cruisers was automatically removed from the R/3 system inventory, let’s take a quick look at the available inventory.

From the SAP Easy Access Menu: Logistics-> Materials Management -> Inventory Management-> Environment -> Stock è Stock overview

Enter BC-S in the Material box.
Enter your Arizona Plant in the Plant box.
Enter 30 for Storage location.

Make sure Display version is set to 1, and click the execute button (looks like a small clock with a green checkmark). Then Stock Overview screen should now be displayed. Look at the number in the Unrestricted use column. It should be 20 less than the ATP number you wrote down in the first exercise.

Now that the delivery of the S Beach Cruisers has sent, and the cruisers have been removed from SOS inventory, Southwest Recreational Vehicles can be billed for the purchase. Let’s walk across the hall and visit SOS’s billing/accounts receivable employee, Tom Hudson.

>>>Next>>>

Sales and Distribution Process Online Learning

2008-02-04T04:50:00.000-08:00

>>Previous>>

Creating delivery for a sales order

Since the Southwest Recreational Vehicles order is due to be delivered in two days, and SOS has enough S Beach Cruisers to fulfill the order, the Beach Cruisers will be loaded and shipped today. This will allow them to be driven to Phoenix, and delivered in two days time. After Keith posted the sales order document, the sales order was automatically entered into the SAP R/3 system shared database. This means that the sales order information is automatically, and instantly, available to the shipping department. Once again, this is accomplished without the use of paperwork.

Once the SOS shipping clerk, Clara Smith, sees that a new sales order has been posted, she checks the delivery date on the document. Noticing that the order must be shipped immediately, Clara creates a shipping document for the order.

From the SAP Easy Access Menu: Logistics è Sales and distribution è Shipping and transportation è Outbound delivery è Create è Single document è With reference to sales order

Enter SPBC (shipping point, Beach Cruiser) for Shipping point.
Enter the order delivery date for the Selection date (two days from today).
Enter the sales order document number from the last exercise for Order.

Click enter, and you will be taken to the Outbound Delivery Create screen. The sales order information should already be entered on the form. At SOS there are three storage areas. Storage area 10 is the raw materials warehouse. Storage area 20 is the Work In Progress area. Storage area 30 is the Finished goods shipping area. Clara must record the storage area from which the Beach Cruisers will be taken (many businesses have several different warehouses to ship inventory from).

To do this, highlight the line for BC-S, and click the Item details button on the bottom of the screen (looks like a small magnifying glass on the left part of the screen). Now click on the picking tab. In the SAP R/3 system, the term picking refers to the physical act of taking goods out of inventory storage for a delivery.

You will notice that the pick status on the lower left portion of the screen shows that the order has not yet been picked. Enter 30 in the Stor. location box to tell the system that the Beach Cruisers will be picked from the finished goods shipping area. Click save, and record the delivery document number displayed at the bottom of the screen on the information sheet. At this point, Clara tells the loading employees in the warehouse to place 20 S Beach Cruisers in delivery trucks. After the loading employees report to Clara that the S Beach Cruisers have been loaded, she returns to the delivery document to enter the amount picked.

>>>Next>>>

Sales and Distribution Process Online Learning

2008-02-04T04:45:00.000-08:00

>>Previous>>

Creating a sales order

The SOS sales division consists of one full time employee. Before SOS implemented their SAP R/3 system, three full time employees were needed to keep track of, enter, and forward incoming sales orders. Due to SAP’s ability to store, produce, and forward sales information, a single employee can now easily complete all the necessary functions.

Upon arrival to the SOS sales office, it is learned that the manager of Southwest Recreational Vehicles is on the phone and is ready to turn the sales inquiry created earlier into a formal sales order. The SOS sales order employee Keith Brown, has learned from the Southwest Recreational Vehicles manager that he wishes to place an order identical to the inquiry created by Patty Teller. After asking for the inquiry number, Keith goes about creating the sales order.

From the SAP Easy Access Menu: Logistics è Sales and distribution è Order è Create

Enter OR for Order type.
Enter your sales organization in the Sales organization box.
Distribution channel will be WH for wholesale.
Division will be BC for Beach Cruiser.

Since the customer does not wish to change any of the information on the inquiry, Keith clicks the Create with reference button (click the Create with reference button now). A pop-up box will appear, with the quotation tab showing. We will be referencing an inquiry for this sales order, so click on the inquiry tab. Now enter your inquiry number from the last exercise, and click the copy button. You should now be at the Create Standard Order screen. The information from the Southwest Recreational Vehicles inquiry has already been entered. Enter the customer initials and date in the Purch. Order no. box (SWRV and today’s date), and click enter. You might see a pop-up telling you that the document is incomplete. Disregard this warning and click save. Record the sales order document number, which will flash across the bottom of the screen, on the information sheet. Keith gives the sales order document number to the customer for future reference, and thanks the customer for the order. That’s all there is to creating an order using the SAP R/3 system.

Now that the formal sales order has been created, why don’t we go next door to the SOS shipping warehouse to watch what they do with the sales order. It is important to note that we will not be taking any paperwork to the shipping department. In fact, none of the transactions so far have required any paperwork to change hands. This means that everything is kept accurate and available in the R/3 system. At no time can writing be smeared or erased to accidentally change the order agreed upon during the initial sales call made by Patty.

>>>Next>>>

Sales and Distribution Process Online Learning

2008-02-04T04:25:00.002-08:00

>>Previous>>

As you can see, the rest of the inquiry form looks very much like a blank order form. On the first line of the blank order form, enter BC-S under material. Now enter the amount of Beach Cruisers (20) under order quantity. After Patty confirms that no Beach Cruisers model S need to be ordered also, she presses the enter button (press enter button now). Notice that the R/3 system fills in the rest of the form automatically. Now let’s check the availability of the Beach Cruisers to see if there will be enough in stock to make delivery. Highlight the BC-S line by clicking the small gray box to the left of the Item column. Now select Environment from the menu at the top of the page, and choose Availability.

You should now be at the Availability Overview screen. Look at the Cum. ATP qty column. This is the Cumulative Available To Promise quantity. If this number is equal to or larger than the quantity ordered, SOS has enough S Beach Cruisers to fulfill the order. Record the number of S Beach Cruisers available to promise on the attached information sheet. As you can see, SOS has enough S Beach Cruisers, and will easily be able to fulfill the order for 20. After informing the manager of Southwest Recreation Vehicles that the Beach Cruisers can be delivered on the date he requested, Patty clicks the green back button to return to the inquiry order form screen (click the green back button now). Patty now needs to access the pricing information to confirm the sales price with the customer.

To view the pricing information of the inquiry; highlight the BC-S row, and click the Item conditions button at the bottom of the screen (looks like a small yellow coin with the number 5 in it). You will be taken to the Item data screen. On the left side of the screen, you will see pricing and cost information on a per unit basis. The numbers on the right side of the screen show the totals for the current inquiry. As you can see, the per unit price of the S model Beach Cruiser is $1,000.00. The cost to produce the Beach Cruiser is $500.00, leaving SOS with a gross margin of $500.00 per unit sold. Patty looks at the right side of the screen, and informs the customer that the 20 Beach Cruisers will cost $20,000.00. She can also see that the sale will be profitable by looking at the $10,000.00 gross margin resulting from the sale. After the customer agrees to the price, Patty returns to the inquiry order screen using the green back button (click the green back button now). As the inquiry is acceptable to both her and the customer, Patty clicks the save button, and writes down the document number which flashes across the bottom of the screen (click save and record the document number on the information sheet). Patty writes the inquiry document number on the back of one of her business cards and gives it to the Southwest Recreational Vehicle manager. As is the procedure at SOS, Patty instructs the customer to call the sales staff at SOS to place his order using the inquiry number. Patty thanks the customer, and moves on to her next sales call.

Although some companies create the actual sales orders during sales calls, SOS has found that creating an inquiry helps in many ways. First, the process allows customers to look at their financial position before committing to an actual order. For instance, if the manager at Southwest Recreational Vehicles discovers that his business will not have the cash on hand to make the purchase of the 20 S Beach Cruisers, he simply calls Patty back to change the inquiry. This way no solid information concerning a sale needs to be removed from the R/3 system. Second, many SOS customers must send any major stock purchases to a purchasing division before the order can be confirmed. The manager at Southwest Recreation Vehicles can simply pass the inquiry number onto his purchaser, who can then call the SOS sales division to place the order.

This greatly decreases the amount of paperwork customers must pass around at their own companies. Not only does this cut down on mistakes at the customer’s company, but it lessens the amount of time an SOS sales employee spends on the phone with a customer’s purchasing staff confirming the contents of the order.

Now that the sales inquiry has been saved, let’s go over to the sales division at the SOS home office to see how the inquiry is turned into a formal sales order.

>>>Next>>>

Sales and Distribution Process Online Learning

2008-02-04T04:25:00.001-08:00

>>Previous>>

As you can see, the rest of the inquiry form looks very much like a blank order form. On the first line of the blank order form, enter BC-S under material. Now enter the amount of Beach Cruisers (20) under order quantity. After Patty confirms that no Beach Cruisers model S need to be ordered also, she presses the enter button (press enter button now). Notice that the R/3 system fills in the rest of the form automatically. Now let’s check the availability of the Beach Cruisers to see if there will be enough in stock to make delivery. Highlight the BC-S line by clicking the small gray box to the left of the Item column. Now select Environment from the menu at the top of the page, and choose Availability. You should now be at the Availability Overview screen. Look at the Cum. ATP qty column. This is the Cumulative Available To Promise quantity. If this number is equal to or larger than the quantity ordered, SOS has enough S Beach Cruisers to fulfill the order. Record the number of S Beach Cruisers available to promise on the attached information sheet. As you can see, SOS has enough S Beach Cruisers, and will easily be able to fulfill the order for 20. After informing the manager of Southwest Recreation Vehicles that the Beach Cruisers can be delivered on the date he requested, Patty clicks the green back button to return to the inquiry order form screen (click the green back button now). Patty now needs to access the pricing information to confirm the sales price with the customer.

To view the pricing information of the inquiry; highlight the BC-S row, and click the Item conditions button at the bottom of the screen (looks like a small yellow coin with the number 5 in it). You will be taken to the Item data screen. On the left side of the screen, you will see pricing and cost information on a per unit basis. The numbers on the right side of the screen show the totals for the current inquiry. As you can see, the per unit price of the S model Beach Cruiser is $1,000.00. The cost to produce the Beach Cruiser is $500.00, leaving SOS with a gross margin of $500.00 per unit sold. Patty looks at the right side of the screen, and informs the customer that the 20 Beach Cruisers will cost $20,000.00. She can also see that the sale will be profitable by looking at the $10,000.00 gross margin resulting from the sale. After the customer agrees to the price, Patty returns to the inquiry order screen using the green back button (click the green back button now). As the inquiry is acceptable to both her and the customer, Patty clicks the save button, and writes down the document number which flashes across the bottom of the screen (click save and record the document number on the information sheet). Patty writes the inquiry document number on the back of one of her business cards and gives it to the Southwest Recreational Vehicle manager. As is the procedure at SOS, Patty instructs the customer to call the sales staff at SOS to place his order using the inquiry number. Patty thanks the customer, and moves on to her next sales call.

Although some companies create the actual sales orders during sales calls, SOS has found that creating an inquiry helps in many ways. First, the process allows customers to look at their financial position before committing to an actual order. For instance, if the manager at Southwest Recreational Vehicles discovers that his business will not have the cash on hand to make the purchase of the 20 S Beach Cruisers, he simply calls Patty back to change the inquiry. This way no solid information concerning a sale needs to be removed from the R/3 system. Second, many SOS customers must send any major stock purchases to a purchasing division before the order can be confirmed. The manager at Southwest Recreation Vehicles can simply pass the inquiry number onto his purchaser, who can then call the SOS sales division to place the order.

This greatly decreases the amount of paperwork customers must pass around at their own companies. Not only does this cut down on mistakes at the customer’s company, but it lessens the amount of time an SOS sales employee spends on the phone with a customer’s purchasing staff confirming the contents of the order.

Now that the sales inquiry has been saved, let’s go over to the sales division at the SOS home office to see how the inquiry is turned into a formal sales order.

>>>Next>>>

Sales and Distribution Process Online Learning

2008-02-04T04:06:00.000-08:00

>>Previous>>

SAP Sales and Distribution Tutorial

In this tutorial, you will learn how to enter sales orders, create delivery documents, post goods issues to customers, and receive payment for SOS Beach Cruisers.

For this demonstration, we will look at the sales and distribution process as an order for 20 S model Beach Cruisers is taken by one of SOS’s salespersons, Patty Teller.

Creating a sales inquiry

During a weekly sales call, Patty Teller contacted the manager of Southwest Recreational Vehicles. Southwest Recreational Vehicles is one of SOS’s wholesale customers located in Phoenix. Currently SOS sells Beach Cruisers to both wholesale and direct sales customers. SOS tried retail sales a couple years ago, but discontinued the practice due to increased sales costs, and large levels of uncollectible accounts receivable.

Through a conversation with the manager of Southwest Recreational Vehicles, Patty discovered that the Beach Cruiser S is selling rather well. As a matter of fact, Southwest Recreational Vehicles just sold the last of their initial stock of 5 Beach Cruiser Ss earlier in the day. The manager of Southwest Recreational Vehicles has decided to purchase 20 additional S models immediately, with the promise of a larger order dependant upon the speed in which he can sell the next 20 cruisers.

Patty’s first step in the sales order process is the creation of a sales inquiry. By creating a sales inquiry, Patty will be able to check the pricing of the potential sales order, and check inventory status. This allows the manager at Southwest Recreational Vehicles to say yes or no dependant upon pricing or delivery date before a final sales order is entered into SOS’s SAP R/3 system. Now let’s create the sales inquiry for the order of 20 Beach Cruisers for Southwest Recreational Vehicles.

From the SAP Easy Access Menu: Logistics è Sales and distribution è Sales è Inquiry è Create

Enter IN for Inquiry type.
Enter your sales organization in the Sales organization box.
Distribution channel will be WH for wholesale.
Division will be BC for Beach Cruiser.
Click the enter button. You will be taken to the sales inquiry initial screen.

Leave the inquiry box blank. SOS’s R/3 system has been configured to generate the inquiry number automatically. This is to prevent different salespersons from issuing the same inquiry/sales order numbers to different customers.

In the Sold-to-party box, select Southwest using the dropdown menu (click inside the Sold-to-party box, then click the small round gray button that appears to the right of the box; then click enter to see the options). Leave Ship-to party blank, as the Beach Cruisers will be shipped directly to Southwest Recreational Vehicles. In the Purch. Order no. box, enter a number to be used as a reference. SOS asks sales persons to enter the customer company’s initials and the date (enter SWRZ and today’s date).

On the Item overview tab, enter today’s date for Valid from. Enter a date one month from today in the Valid to box. By entering these dates, you are telling the R/3 system that this inquiry, and any pricing or product amounts therein, is valid for one month from today.

Although Southwest Recreation Vehicles is not receiving any type of discount for this order, SOS does offer price breaks during high volume months if customers place orders and take shipment within a week of the sales inquiry.

This procedure is used to keep finished goods stock low, saving SOS inventory costs. The inquiry validity dates allow salespersons to make discounted prices good for only one week during the high volume months. After the week is up, the inquiry containing the price break is no longer valid, and a sales order without a discount will be created.

Now enter a date two days from today in the Req. deliv. Date box.This is the date that the manager of Southwest Recreational Vehicles wishes to take delivery of the Beach Cruisers. Record the delivery date on the attached information sheet.

>>>Next>>>

Sales and Distribution Process Online Learning

2008-02-04T03:28:00.000-08:00

>>Previous>>

4. Inventory Levels for a Material

From the SAP Easy Access screen, choose Logistics->Materials Management->Physical Inventory->Environment->Stock Overview.

Use material P-109. No other entries are needed. Do not press Enter. It is useless in this context. Instead, click on Execute (the green checkmark with a clock behind it).

The table shows the company code and name (there are several different “companies” in this SAP system), the plant code and name, the storage location code and name, and the batch.

What is the total inventory in unrestricted use? ___________________

How many pieces are in the New York plant? ______________________

This time use the Exit button to go back to the SAP Easy Access Menu in just one step instead of using repeatedly (Backward Arrow)

5. Document Flow

Now we want to see all documents that are part of the chain including this order.

From the SAP Easy Access Menu, choose Logistics->Sales and Distribution->Sales->Order->Display.

Put the order number in: 5404

If you select (Enter) at this point it will display the order document. However, from this
Display Sales Order Initial Screen, you can also go directly to the document flow display by clicking , the document flow button on the buttons line after the white bar displaying the window title.

You can see all documents in this chain. You will see the order itself, the delivery document which is summary document needed to control delivery, along with the detailed documents showing the steps in the process.

The transfer document records that the items ordered are no longer available, and is used to create a picking document.
The goods issue documents says that picking is complete and the items are no longer on the shelf. The invoice says the items have been billed, and the accounting document gives the related accounting entries. We will go into each of these document and the processes they relate to in more depth, as we get deeper into the course.

6. Explore some more

If you have more time, go back and explore the same general material with another customer order: 5729. SAP is a strange beast – very powerful, very complex, and easy to get confused about. It is a tiger, and you now have it by the tail! Best to start getting to know it.

>>>Next>>>

Sales and Distribution Process Online Learning

2008-02-04T03:10:00.000-08:00

>>Previous>>

3. Material Master Tables

Now we will look at master table information on each material (product), using the material from the above order as our example.

From the SAP Easy Access screen, select Logistics ->Materials Management -> Material Master ->Material->Display->Display Current.

Use the material from the example order, which is P-109. Choose (TIck) button or just press Enter.

Now check the tables you want to see. Check the following views: Basic Data 1,

Sales: General/Plant Data, and Costing 2. Scroll down and use any of the following (DownArrow) buttons to get to the Costing 1 view.

Choose (Tick) to continue.

In the Organizational Levels window, click on Plant to see which plants this material is located in. Choose the Werk Hamburg plant by double clicking on it,and then choose (Tick) to continue.

It seems you get all the data, even if you only asked for a few tables. Notice, however, that the ones you checked are specially marked .

Under (Basic Data1) tab

What is the description of the material? __________________________

What is the unit of measure? ______

What is the gross weight? ___________________

Under (sales:General/Plant) tab

What are the transportation group and the loading group? ____________________

To see what the other possibilities are for transportation group and loading group, click once on the field with the value, then click on the listing icon that will become visible. Use the browser back command to return.

What is another possible transportation group, beyond pallets?

What is another possible loading group beyond cranes? __________________________

Under (costing2) tab

What is the standard price? _______________________

Is this what was charged on the order? ___________________

(1 DEM = 0.51129 EUR)

Why might these two be different?

Now lets look at inventory levels for this material. Back out to the SAP Easy Access initial screen by repeatedly using (backward arrow ) on the button bar below the SAP menu bar.

>>>Next>>>

Sales and Distribution Process Online Learning

2008-02-04T02:48:00.001-08:00

>>Previous>>

2. Customer Master Tables.

Now we wish to look at some of the data that SAP stores about each customer. This data is the source for much of the information that goes on the order you have already looked at. (The order requires a customer identifier (sold to party) and automatically fills in much of the information from that.)

We will use the sold-to party from the earlier document. Start at the SAP Easy Access initial screen.

Choose Logisticsà Sales and Distribution à Master Data à Business Partners à Customer à Display à Complete.

For customer, enter the identifier 1400 for the sold to party from the earlier order document.

On the Sales Area, select the (CustomerSalesAreas) button.

A customer can conceivably purchase material from several different sales areas. In this case, there is just one Sales Area: 1000/10/00, which is the one used in Sales Order 5404. Double click on that line to import the data into the “Display Customer: Initial Screen”. Choose (Tick) botton to continue.

By looking into the several areas for general data, answer the following questions:

How many employees does the firm have? _______

What industry are they in? ___________________

Who is the contact person and what is his function?

What is the name of the person who serves as the Sales employee partner in this relationship? (Hint: Look into (Sales Area Data) Tab __________________

Return to the SAP Easy Access initial screen by using ((X)Cancel buttons)

>>>Next>>>

Sales and Distribution Process Online Learning

2008-02-04T02:34:00.000-08:00

>>Previous>>

Look at an existing order

Go back to “Display Sales Order: Initial Screen” (follow the menu path: Logistics à Sales and Distribution à Sales à Order à Display)

For the order number, use 5404. You don’t need to fill anything else out.
Choose (or press the Enter key).
You will see the overview of the document, which includes much of the header information. You won’t have to understand all the information on these documents, but you will need to understand some of it.

Who is the sold-to party for this order? (Get the customer identifier and the name --You’ll need this later.)

Identifier _______, Name ___________________

Who is the ship-to party? ____________________________________________

Under what circumstances might they be different? ________________________

Now look at the order lines. What “Material” (i.e. product code) is being ordered? You will need this later.___________________

What quantity is being ordered? ___

What is the description of the material? ____________________________

You are looking at the Order Overview screen, which has only some of the Header information, and some of the line item information. Note that you have a number of tabs you can choose from. Use the Shipping tab.

What is the total weight in kilograms for this order? ___________________

What is the delivery status? ___________________

Under what circumstances would you get a different answer to the previous question? _____________________________________________________

You can look at the rest of the Header information by going to Header Details as follows. On the Display Standard Order 5404: Overview screen, note the magnifying glass just above the tabs, on the right. Place your cursor over it and you will see what it does (shows “Display doc. header details”). Click on the magnifying glass. Note that you now have more tabs you can choose from.

What kind of information is now available at the Details level that was not before at the Overview level?

You can use the left arrow on the green ball (on the button bar) to back out to the overview screen to compare. You can also use the left or right arrows at the right of the tabs to bring other tabs into view, or get a list of the tabs by clicking on the list icon to the right of the arrows.

(Give one example of new info at the details level ) __________________

Choose the Partners tab.

Who will be paying for this order? ___________________

Choose the Status tab.

What is the rejection status of this document? _____________

Note the delivery status that you have already obtained. You will notice while using SAP that you can find the same information either in different locations or in the same location reached through different ways.

On the Main Menu (dark blue bar on top), from the “Goto” dropdown menu, choose Overview. (Goto à Overview).

Now look at the schedule lines for a line item. (A line item is a particular material that is ordered. The schedule lines tell when parts of a line item will be delivered etc. There may be more than one schedule line for a line item, if not all is delivered at the same time.) On the Display Standard Order: Overview screen, select the first line item by clicking to the left of the line (toward the bottom). The line will turn dark yellow.

Having selected the line, go to the bottom of the form and click on the Display Item Details button . (You may have to use the scroll bar on the right to down to the bottom of the screen to see the buttons.)

Once again you have tabs to choose from. Select the Schedule Line tab. Then choose the line with a confirmed quantity by clicking on the corresponding blank button on the left side of the quantities/dates table (line turns dark yellow). Now click on the magnifying glass at the bottom left (Sched. line-detail).

On the Display Standard Order 5404: Schedule Line Data screen, choose the shipping tab.

What is the material availability date (the date the material is in the warehouse and ready to be delivered)? ___________________

What is the loading date? ___________________

What is the delivery date? ___________________

Return to the Display Standard Order: Item Data screen by clicking (the green back arrow icon at the top of the screen).

Select the Shipping tab.

Who is the ship-to party? ___________________

What is the unloading point at the ship-to party’s location? __________________

What plant of IDES is this coming from? ___________________

Select some of the other tabs to see what information is available. Some information is not filled out, since it has not been entered, but much of it is available.

Now choose the Condition tab. This shows information used in pricing and discounting the sale, as well as things like cost and profit margins. Use the down arrows to also see the bottom portion of the table. What is the cost per item?

how much tax is charged for this line item? __________________

Is there any discount? ___________________

Use twice the cancel button at the top of the screen to back out to the initial SAP Easy Access screen.

>>>Next>>>

Sales and Distribution Process Online Learning

2008-02-04T02:21:00.000-08:00

>>Previous>>

Before you begin: We will spend a good part of the course learning to use, understand and configure this system. Don’t rush through the exercise. Explore rather than merely putting in the required keystrokes. Think about the system as you go. Get a feel for how it works, how it is structured, what it can do for you. How easy would it be to learn to get around using this SAP interface? How powerful is it in terms of supporting a business?

Basics

As you look at the screen, notice that the top four lines of the screen are familiar Internet Explorer information and controls. We will generally ignore these, though the very top of the screen has the title of the window on shaded blue background, and this will be useful. In this case it is “SAP Easy Access”, the system’s initial window.

The next three lines are SAP information and controls.

First, on a dark blue background, you will see the SAP main menu comprised of five dropdown menus: “Menu”, “Edit”, “Favorites”, “Extras”, “System”, “Help”, and “Function”. Click on one of these and then run your cursor over the menu choices, and you will see drop down boxes that show you the sub selections.

If a sub selection has a black triangle to the right, then there are further levels of sub selections available. Later, after having finished the class, you may select “Log off” on the “System” dropdown menu to abandon the SAP system (or you may use a shortcut – you will discover it once you read the next paragraph).

Below the main menu bar is the button bar that surprisingly enough contains buttons to perform common actions. Some of the buttons are enabled such as the “Enter” (green check mark) button while others are disabled such as the “Save” (disk picture) or the “Back” (back arrow) buttons. Running your cursor over the enabled buttons will disclose their function. The buttons disabled will get enabled once the context allows it.

Below that is the title of the window, this time with a white background. (This is a repeat of the top line of the whole screen, the Internet Explorer information). In these exercises we will often refer to the window names as a way to help you know if you are “on track”.

From this point on, you will get to the specifics of a particular screen. Right now, you are on the “SAP Easy Access” screen as shown in the white bar. Some buttons you may use on a particular screen are presented on the next level. “SAP Easy Access” also provides you with a folders list you can use to navigate in the same way you are used to in a Windows-like environment.

To see how this works, let’s look at how we can take actions or get information relating to customer orders. Double-click on the Logistics folder, and then move down and double-click on the “Sales and Distribution” folder. (You can also single click on the triangles to get the same result.) Double-click on “Sales”, and then on “Order”. You have reached the point when you can execute a transaction. Double-click on “Display”. You will see the white bar changing the title from “SAP Easy Access” to “Display Sales Order: Initial Screen” as well the title of the window on the very top. You have now a menu bar with different choices, appropriate for the task at hand. The standard button bar below the menu bar remains the same, except for the button that is now enabled: the “Cancel” (cross mark on a red globe). Select the “Cancel” button to abandon this transaction (or any other transaction without saving any data). You are back to the folders list. Click on the “SAP Menu” button, the first enabled button after the screen title to go back to the compact view of the folders list. We are going to start from this point again.

>>>Next>>>

2008-02-04T02:13:00.000-08:00

>>Previous>>

Getting acquainted with the SAP R/3 Interface (Release 4.6 C),

and the Sales and Distribution Process.

This exercise starts from the “SAP Easy Access” initial screen. Your instructor will lead you through the log-on process to get you to this screen.

In this exercise we will assume we are part of the IDES Company, which sells motorcycles, and accessories, etc.

We will do the following:

1. Look at an existing order to identify information on the header, the line items, and the schedule lines for the order.

2. For the customer referenced in the order, we will look at the customer master tables to identify certain information carried on the system.

3. For the material referenced in the order, we will look at the material master tables to identify certain information carried on the system.

4. Check the inventory for that material.

5. Look at the document chain for this document, that is, the string of subsequent documents that all relate to this order.

>>>Next>>>

2007-12-16T00:16:00.000-08:00

Q. Can Sales Order and Billing Have Different Pricing?

Yes, can have 2 different pricing procedures

1. One for Sales Order

2. Another at the Billing

Let us take an example :

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

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

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

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

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

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

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

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

2007-12-15T23:53:00.000-08:00

Q. Steps To Setup Collective Billing in SD

Collective Billing

Configuration steps:-

Transaction VD02 - Change Customers - tick Billing and filled in the Customer Code, Sales org., Distr.channel and Division then hit enter.

Look for field name Inv.list sched. - you must filled in the Factory Calendar that you are currently using.

You can simulate the collective billing in transaction VF04 - Process Billing Due List.

During simulation, if the billings cannot be combine, the system will give you this message,

Different header fields $000000001 $000000002
Combination criteria in the billing xxxxxxxxxxxx123 xxxxxxxxxxxx125

Criteria to satisfy for collective billings:-

Billing document type is the same.

Reference document type is the same.

Item category in the reference document is the same.

The system combines into one billing document all transactions for the same customer and same billing data. If the header data and the header partners for the specified deliveries or sales orders are identical and if the requirements for splitting do not apply, one billing document is created for all the deliveries or sales orders.

The Following illustrates an example. The system determines that deliveries 1 and 2 had the same bill-to party, and therefore combines the deliveries in one billing document.

Delivery Order 1 - |

-----------> Invoice

Delivery Order 2 - |

2007-12-15T23:21:00.000-08:00

EDI Configuration Phase

"Once your design has been thoroughly thought through, and project management approval has been achieved the detailed configuration can commence. Prior to this phase some configuration work may have been done to determine the best way to achieve your desired goal. To configure EDI in SAP you can utilize numerous settings and programs to configure the solution in a multitude of ways. We document a few for you to browse through below."

This section describes how to proceed with the implementation of an EDI solution. The selected EDI mapping tool will also determine the details of some of the steps that has to be followed.

Install EDI mapping tool

The selected EDI mapping tool has to be installed and tested for technical correctness.

Environment control

The selected EDI mapping tool should be set up to allow users to log onto and use the system. This steps also includes the configuration that has to be done on the EDI mapping tool for each trading partner. This step will be repeated when new trading partners are added.

EDI mapping

This step is dependent on the actual EDI mapping tool selected, but certain concepts has to be considered and followed nevertheless.

Mapping defines the relationship between an application data set and a target EDI standard, and vice versa. Mapping is usually divided into two phases: application definition and transaction mapping. In application definition, you determine what your application data set looks like. In transaction mapping, you tell the mapping tool how to map the data from application to EDI standards (and vice versa). Transaction mapping defines the relationship between data fields in your application and EDI data elements.

Generic templates or mapping tool specific templates should be used for this task.

Communication

Communication involves the actual sending and receiving of data to and from your trading partners. The way communication works is dependent on the EDI mapping tool and the communication technicalities selected.

Prepare Scheduling

The scheduling requirements for EDI communication and processing as defined during the planning/design phase of the implementation should be implemented. The tools selected and the functionality they provide will determine the implementation details. This includes things like scheduling communications sessions and mapping jobs.

2007-12-15T22:34:00.000-08:00

General command field formats

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

2007-12-08T06:59:00.000-08:00

Create Purchase Order ME21N

Idea

Use this procedure to create a Purchase Order. While there are many different types of Purchase Orders that can be created (using different document types) this document addresses the following types:

· Standard PO

Use this document type (NB) to procure standard Catalog and Non-Catalog materials. This document type is subject to an approval release strategy depending on total dollar value.

· Stock Transport Order
Use this document type (UB) to create a Purchase Order where the supplying vendor is another DTE plant. This document type is subject to an approval release strategy depending on total dollar value.

· Emergency Purchase Order
Use this document type (ZEPO) to create an emergency Purchase Order. This document type is not subject to an approval release strategy.

· Consignment Purchase Order
Use this document type (ZCON) to create a vendor consignment Purchase Order. This document type is subject to an approval release strategy.

· Vendor Managed Inventory Purchase Order (ZVMI)
Use this document type (ZVMI) to create a Purchase Order for materials subject to Vendor Managed Inventory. This document type is subject to an approval release strategy.

This document demonstrates how to create a Standard Purchase Order for both a Catalog item and a Non- Catalog item. Please note that the screens and field selection for an Emergency Purchase Order and a Consignment Purchase Order are identical to that of a Standard PO. When creating a Stock Transport Order, the only difference is that the “Vendor” field becomes the “Supplying plant” field.

Menu Path

Use the following menu path(s) to begin this transaction:

· Logistics >> Materials Management >> Purchasing >> Purchase Order >> Create >> ME21N - Vendor/Supplying Plant Known

Procedure

1. Start the transaction using the menu path or transaction code ME21N.

2. Perform one of the following:
If Go To You are going to create a Purchase Order manually from scratch Step 9
You are going to create a Purchase Order with reference to a Requisition, an existing Purchase Order, a Quote, etc. Next step

3. Click Document overview on

4. Click the button.

5. Select the type of document from which you wish to create the Purchase Order.

7.The data will display based on the criteria you entered. When you have found the correct document you can click on the document to adopt the entire document or you can just click on one of the line items if you only want to adopt the data from one line item.

8.Click the Adopt button once you have highlighted the document (or specific line item) you wish to use to create your Purchase Order. The Purchase Order will populate the fields it is able to from the document you selected. Make sure you validate all of the data that is pulled over in the following steps.

9. At the Header level, complete/review the following fields:

Field Name Standard PO (Document Type)

R/O/C R

Description Identifier allowing differentiation between the different kinds of purchase orders in the SAP system. From the drop-down menu select the proper document type.

Example: Standard PO

Field Name Vendor

R/O/C R

Description Number and name of the vendor (external supplier) or supplying plant from which the materials are to be procured. Enter the vendor number and both the name and number will display.

Example: 800089

If you are doing a Stock Transport Order (by choosing Document Type “Stock transport ord.”), note that the main difference between it and a regular purchase order is that the “Vendor” field becomes the “Supplying plant” field. In stock transfer processing, goods are procured and supplied within a company. One plant orders the goods internally from another plant (receiving plant/issuing plant). The goods are procured with a special type of purchase order - the stock transport order.

continued...

2007-12-08T04:12:00.000-08:00

>>PREVIOUS>>

Understanding Material Determination

Assigning Procedures to Sales Document Types:

In this step, we would assign the above procedure to Sales Order document type.

Go to Transaction OV14 or go to Transaction SPRO -> Reference IMG -> Sales and Distribution -> Basic Functions -> Material Determination -> Assign Procedures to Sales Document Types (As shown in the screenshot below)

Scroll down the list for the order “OR” (Standard Order)

Now to maintain the substitution reasons:

Go to Transaction OVRQ.

In this screen, you can maintain the substitution reasons.

Maintaining Materials for substitution:

Go to Transaction VB11 or follow the navigation shown in the screenshot below:

Enter the condition type in the above screen and click on Enter.

Maintain the substitution material information and click on Save.

Testing

To test the condition records, let us go to transaction VA01 or VA02:

In the above screenshot, we have entered the material T-F299. Now press ENTER.

In the above screenshot, you can observe that the material is automatically converted from T-F299 to T-F499.

>>NEXT>>

2007-12-08T03:38:00.000-08:00

>>PREVIOUS>>

Understanding Material Determination

Following list appears:

For our demo purpose, we would go ahead with this condition table.

Go back to the earlier screen.

Now click on “Maintain access sequences”. Access sequence is a sequence of steps SAP follows in order to obtain the condition record.

Select A001 and click on “Accesses”

In the above screenshot, the first field “No” is the access number. The access number is the order in which the system will read the access sequence. For e.g., if the access numbers are 5,10,12,15 and 20, then the system would start with the lowest entry (in this case it is 5). It would proceed further to 10 if it is not able to process 5. If no record found, then no material determination would be carried out.

Select the record and click on Fields.

Now let us check out the Condition Types available. Go back to the earlier screen and click on “Define condition types”. Following screen appears:

Now let us check out the procedures configured in the system:

Select a procedure and click on control data.

>>NEXT>>

2007-12-08T02:59:00.002-08:00

Understanding Material Determination

Material Determination is a technique to determine the material to be used in the Sales Order. For e.g.,

Substituting one Material to another in the Sales Order.
Special gift-wrapping of a material for a festive season.
Swapping customer’s material number to our own material number.

To configure the Material Determination:

Go to SPRO -> Reference IMG -> Sales and Distribution -> Basic Functions -> Material Determination -> Maintain Prerequisites for Material Determination (As shown in the screenshot below):

We would go by step-by-step for the Material determination.

The first step is “Maintain field catalog”. This screen can also be accessed from the transaction OV26.

Field catalog contains fields used by the system to determine substitution materials in the Material Determination procedure. Click on “Maintain field catalog” in the screenshot above. Following screen appears:

For our demo purpose, we would work on only MATNR (Material Number). Scroll down the list to find the field MATNR.

Click on Backspace and come back to the main screen:

Click on “Display Condition tables”

Use F4 help to select a table.

Select 001 from the list and press Enter.

>>NEXT>>

2007-12-08T02:43:00.000-08:00

SAP SD Interview Questions And Answers

What is the purpose of text determination, account determination, partner determination, output determination, storage location determination

Answer1:

Text determination: For transferring information from material or customer to order/delivery or invoice (and anything in between)

Account determination: For transferring financial and costing information to proper financial docs

Partner determination: For determining who is is legally responsible for A/r, who the goods are going to and whatever else you waana drive through this functionality.

Output determination: What kinda output does a sales/delivery/billing document create and who gets it, where?. For example A partner might get an EDI notification for a sales order just confirmed, whereas a financial/leasing company gets the invoice!

Answer2:

(a) Text Determination: Any Texts in Masterial Master/Material Determination/Order/Delivery , etc is meant to convey messages to the subsequent documents for compliance. e.g. "Give Top Priority" message mentioned in Order is meant for Production Dept.

(b) Account Determination:is integration between Finance and SD. The A/P along with Account Keys need to be allocated accordingly with combination of Account Determination Group for Customer and Material if required.

(c) Partner Determination: To identify which type of Partner it is so that if required for same Customer different Partner Functions may be required e.g Only One Sold To Party per Customer. More than One Ship to Party/ Bill to Party/ Payer possible. Accordingly different Masters will have to be created. Useful for dispatch of Material in casae of Ship to Party, sending Bill in case of Bill to Party and payment followup/Dunning in case of Payer.

(d) Output Determination: What type of Output (Fax/Mail, etc) is required, where and in what Format(ABAP Customisation may be required in some cases especially Invoices).

(e) Storage Location Determination: depends on Plant, Shipping Point and Storage Conditions

What are the five imp fields to be maintained in account determination

Account Determination: Sales View, Sales Organization, Distribution Chanel, Chart of Accounts, Account Assignment Group for Customer and Material and Account Keys.

What is meant by transfer of data from legacy code to sap Legacy Code ?

Answer1:

It should be legacy data to SAP. What it means is you want to transfer all the customer and materials and all other information from Older (legacy system) to new SAP system. You can do it using many tools, most noticeably MDMs.

Answer2:

Before installation of SAP, Data maintained by Company is called Legacy Data. At the time of installation, it is required to transfer Data from Legacy to SAP like Masters (Material/Customer, etc). It can be done in various ways like BDC, LSMW, etc.

What do you do really in pricing determination, and what are the main deifferences between pricing procedures?

Answer1:

Pricing is determined by combination of Sales Organization, Distribution Channel, Division, Customer Pricing Procedure and Document Pricing Procedure.

Answer2:

We determine how the prices are calculated, taking into account sales area(sales org, distribution channel, division), document type and customer(generally sold-to-party).

The main differences between pricing procedures would be the differences as we mentioned above, from the point of view of field entries. Coming to the output and the procedure, Suppose the condition types used will be different and hence the following whole procedure. One pricing procedure determination to the others, which data control these differences

What type of reports generally a support consultant maintain and report

Depends on Customer requirements.

What is the purpose of shipping point determination not menu path

So that Shipping Point is determined automatically once the settings for the same are done.

What and where types of copy controls we change

Copy Control: is basically meant so that Data is copied from preceding Document to subsequent one. What subsequent Document is required is to some extent determined by Customer Requirements as well as Document Types. e.g. In general case of Standard Order, it will be Copy Control (Order to Delivery) from OR to LF .

How to and where to maintain copy controls

Check for yourself in IMG (Sales Document types and Delivery Document Types)

What is purpose of maintaining common distribution channels and common
divisions

Common Distribution Channel and Common Division are maintained so that if any master data like customer or material maintained with respect to one distribution channel can be used in other DCh. It prevents the multiplication of master records.

Eg: A customer is created for say sales area 1000/20/00 then the same customer can be used in sales area 1000/30/00 if we maintain 20 as common distribution channel. Hence no need for extending the customers...the same for materials also.

What is the difference between the Availability check 01 (Daily requirement) and 02 (Individual Requirement) in material master?

01 and 02 are the checking group. Availability check is carried out with the help of these checking group and checking rule. Checking group 01 and 02 are maintained on the material master.

01 - Individual requirement -For this system generates transfers the requirement for each order to the MRP .So that MM can either produce or procure.

02- Collective requirement.-In this all the requirements in a day or in a week are processed at a time. System stores all request and passes on to the MRP in MRP run. In this system performance is high however you can not do the backorder processing whereas in other you can do.

2007-11-24T03:50:00.000-08:00

Marking reference field as mandatory when posting a document

(Customer invoice, Vendor invoice, Customer Credit Memo and others)

This document details the procedure in marking the reference field as mandatory while posting a document like Customer invoice, Vendor invoice, Customer Credit Memo and others.

Go to transaction OBF4

Click on the document type you require. For this demo, let us consider the document type DG (Customer credit memo). Select the document and click on Details.

Following screen appears:

From the above screen shot (the one highlighted), there is an option to mark whether the reference number should be made mandatory or not. Check the check box adjacent to "Reference number".

Now let us try to post a document (Customer credit memo) using the transaction FB01.

Without entering the Reference number, enter the other mandatory information and press ENTER.

Following message would appear:

2007-11-24T03:15:00.000-08:00

Configuring Availability Check

Availability check

Availability check is an integral part of the business process that determines if the required delivery quantity can be met on a required delivery date. For this purpose the system takes into account pre-delivery activities such as scheduling for picking or packing times and the time taken to produce or obtain the material. It also performs several background functions such as Backorder processing, rescheduling and ATP quantities.
Backorder processing: processing of a sales order that has not been fully confirmed or not confirmed at a certain delivery date.
Rescheduling: is a proposal of how – confirmed quantities already assigned to a sales order can be reassigned to other sales orders that have a higher priority.
Available to promise (ATP): is a process of checking the available quantities of a material. The ATP quantity consists of warehouse stock + planned receipts (incoming stock) – planned issues (outgoing stock). to examine stock on hand (CO09) proceed to logistics – sales & distribution – sales – environment – availability overview.
Replenishment lead time (RLT): is the time taken for the material to become available either internally (in house production) or externally (from a vendor). The most important things to consider during an external procurement are purchasing and MRP2 (procurement) views of MMR where the processing time for purchasing, planned delivery time and goods receipt processing time are taken into account. On the other hand internal procurement is based on in house production time (MRP 2 view) goods receipt processing time or alternatively RLT time, which is found on MRP 3 view.
RLT (Replenishment Lead Time) is the time taken for the material to become available. RLT is only used when doing an ATP check (Available To Promise). The value of RLT for a material is specified on material master record.
There are three types of availability checks –
- Check on basis of ATP quantities.
- Check against product allocation.
- Check against planning.

Configuring Availability check through Checking Groups

The checking group + checking rule determine how the availability check is to be performed.
The checking group determines whether and how the system checks the stock availability and generates requirements for material planning. The checking group defines what type of requirements will be passed on i.e. summarized requirements (daily/weekly) or individual requirements for each sales order.
The checking rule applies to how the availability check is to be carried out at the transaction level. Note that you must define checking rules for each individual application such as for production orders for example. In Sales and Distribution, the checking rule is specified internally within the system and cannot be changed.
The checking rule, in conjunction with the checking group, determines the scope of the availability check for every business operation; that is, which stocks, receipts and issues are to be included in the availability check and whether the check is to be carried out with or without the replenishment lead time.
Briefly explaining the above – checking group determines which type of requirement to be passed on to MRP whether it be individual or summarized and checking rule which is at the transaction level and can be configured independently for each application module, determines which stocks, receipts and issues to be taken into account. For performing an availability check checking group has to work in conjunction with checking rule.
Advantages of individual processing over summarized processing –
Backorder processing is possible.
You can access (MD04) order, line and schedule line individually which gives a greater control on available stock and requirements placed on stock.
The system automatically uses individual requirements in case of special stock items.
Required data for the Availability check to be carried out –
The Availability check must be switched on at the requirement class level.
The Availability check must be set at the schedule line level.
A requirements type must exist by which the requirements class can be found.
A plant must be defined in the sales order for each schedule line item (in other words plant must be defined for every material in MMR).
A checking group must be defined in the material master record in the MRP3 screen in the availability check field.
Configuring Availability check and defining Checking Groups –
Checking groups are introduced into the sales order based on the setting in the material master record.
SAP standard checking groups are 01 – summarized requirements and 02 – individual requirements or you can create your own by copying the standard ones.
Total sales and total deliveries columns are there to configure a checking rule to sum up requirements to post to MRP either individually or by day or week.
Block quantity required can be set if you want several users to be able to process the material simultaneously in different transactions without blocking each other.
The no check indicator is CHECKED when you DO NOT want the system to carry out ATP check.
Defining material block for other users – the block check box is an indicator that enables you to block material master records of a particular material during the availability check and restrict other users from accessing same master record and reserve the material. If the block is not set, two users can confirm the same material at the same time for two different orders, not knowing if the stock is available or not. If you select this field, the material is blocked during the availability check and other users cannot: a) Make changes in the material master record. b) Create purchase orders for the material. C) Create orders for the material.
Defining default values for checking groups - Checking groups are introduced into the sales order based on the setting in the material master record.
However if there is no entry present in the material master record for the checking group, a default value can be set here, depending on material type and plant.
This default value will be used by the system depending on the material type mentioned in MMR and plant in sales order.
If an entry exists, this default value is over written by MMR.
Controlling Availability Check – in this section, you tell the system what stock on hand and what inward and outward movements of stock it must take into account when performing the availability check in addition to whether or not to consider the replenishment lead time.
These settings are based on the checking group that is assigned to the material master record and the checking rule that is predefined and assigned to the sales and distribution transaction.
These settings carry out control both for sales order and delivery as well. This is due to the fact that you may want to include specific stock or incoming stock for the sales order, yet at the time of the delivery only include physical stock on hand waiting to be shipped.
It is possible to indicate to the system that you would like the availability check NOT TO CHECK the stock at the storage location level. This indicator is used to set the scope of the availability check.
It is used to switch off the check at storage location level. You create a reservation for a particular storage location. However, the scope of the availability check is set in such a way as to exclude the storage location. In this case, the system carries out the check at plant level only and does not take the storage location into account that is specified in the reservation.
Should you not want the system to automatically check RLT, you may indicate so here. RLT is the time taken for a material to become available. It is only used when doing an ATP check and is taken from MMR.
defining the elements in the availability check entirely depends on the business needs, but a few tips are given under –
When controlling the Availability check at the time of the sales order, a purchase requisition does not necessarily indicate by it is going to come into the plant.
A shipping notification on the other hand - a confirmed purchase order – is a good indicator of receiving stock on a specified date.
It is always recommended not to select the shipping notifications for the delivery requirements type as you may not actually receive the stock into plant or warehouse for which you are creating a delivery.

2007-11-24T02:43:00.000-08:00

Multi-level Packaging in Delivery

Before creating the packaging material you have to go to:

IMG-Logistics Execution-Shipping -Packing.

Define packaging material types- it can be anything like boxes crates, etc. in this you have to maintain the output determination procedure, output type, plant determination, packaging material category, generate delivery items, number assignment. you can copy from standard also.

Then go to define material group for packaging materials - here you maintain the four digit code and the description. Actually, this group is nothing but similar products which require similar packing products. For Ex. Nokia Phones all types they are basically packed first into a polythene bag. So here nokia phones can become a material group for packaging materials and polythene bag can become the packaging material type which can include different sizes and types of polythene bags.

Define Allowed Packaging Materials - Here you assign the shipping group for packaging materials to the packaging material type. This is related to your material master data of the packaging material which you create.

Now go to MM01 to create a packaging material. use material type as Packaging material then inside the system will take the item category group as VERP. Then in the Basic Data1 screen you have the material group for packaging material (MGPM). Select the proper one. Now in the Sales:General/ Plant screen you have to maintain data regarding the packaging. you select the MGPM same as the basic data 1 screen, then select the packaging material type, the allowed pkh weight, allowed pkg volume. This is important because if the weight of your finished item is 2 KG and in the allowed pkg weight you enter only 1.5 KG, then while you carry out the packing process in delivery, the system will give you error," packaging weight exceeded." The assignment in the IMG creen for Define allowed packaging materials should be same as u mention in the material master. Then save your material master for packaging material.

VA01 create the order, save it.

VL01N enter shipping point, go to edit - pack- you will face a screen with 2 parts. In the top part you select your packaging material in which you want to pack your finished item, enter the system will assign a number to that material. Now select the Material in the top part and the finished one in the lower part and click on the Icon Pack. Here one thing has to be taken care of. Suppose if you want to pack only one finished item in one packaging material, then in the lower part of the screen you have a field for partial quantity here you change it to 1. system will prompt quantity changed. now you select the material in the top part and the one in the lower part and click on the PER PART. QTY ICON. In this way the system will pack only one finished item in a single packaging material. Packing is done go back, select the picking and do the PGI. save the delivery and create the invoice.

HANDLING UNITS. (Used for Multi level packing)

Basically handling units come into picture when you want to carry out multi level packing. suppose you want to pack Nokia phone first into a polythene bag, then this polythene bag is again packed in to box. like that. then this box will become a handling unit.

For this go to :

IMG - Logistics General - Handling Unit Management - Basics.

First create all your packing materials using MM01 and type as packaging material. Maintain all the assignments in IMG in Logistics General.

In basics you do the same thing as you did in the packing in logistics execution. like you create the packaging material type, then MGPM and their assignment.

Then go to External Identification - and maintain the number ranges for the handling units that you want and assign the same to your packaging material type.

Now that you have done everything, create the order, save it, in VL01N, enter shipping point, go to edit - pack - do the same thing as i have told you in the step no. 6 (above). now after doing select the PACK HUs TAB . NOW IN THIS SCREEN IN THE TOP PART YOU WILL SEE THE ALREADY PACKED MATERIAL. In that same part again select your next packaging material that is BOX. enter the system will assign the number to the BOX.

Now select the material which you have just entered and the materials which were already packed in the lower part of the screen and click on the ICON PACK.

In the same way again in the top part of the screen you select your next level packaging material and press enter. the system will assign a number to it. now select the material you have just entered and the previously packed material in the lower part of the screen and click on the icon PACK.

In this way you can carry out multilevel packing. just take care of the allowed packing weight and the number of units you have to pack in the next packaging material.

2007-11-24T02:04:00.000-08:00

Enterprise Structure Configuration

Enterprise Structure:

1.Maintaining Sales Organization
Sales Organization is an organizational unit responsible for the sale of certain products or services.

IMG -> Enterprise Structure -> Definition -> Sales and Distribution -> Define, copy, delete, check Sales organization

2. AssigningSalesOrganization to Company Code
This assignment ensures all the sales made through this Sales Organization are accounted for in the assigned Company Code (Company Code is created by FI Consultant).

IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign Sales Organization to Company Code

3. Maintaining Distribution Channel
Distribution Channel is the way, in which Products or Services reach Customers.

IMG -> Enterprise Structure -> Definition -> Sales and Distribution -> Define, copy, delete, check distribution channel

4. Assigning Distribution Channel to Sales Organization
This assignment ensures, a Sales Organization can supply Materials to Customers through this Distribution Channel.
IMG -> Enterprise Structure -> Assignment -> Sales and Distribution > Assign distribution channel to sales organization

5. Maintaining Division
Division is a way of grouping materials, products, or services.

IMG -> Enterprise Structure -> Definition -> Logistics - General -> Define, copy, delete, check division

6. Assigning Division to Sales Organization

IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign division to sales organization

7. Setting up Sales Area
All the sales are made from a particular sales Area. For creating a Sales Order Sales Area is compulsory.

IMG ->Enterprise Structure -> Assignment -> Sales and Distribution -> Set up sales area

8. Assigning Sales Organization- Distribution Channel- Plant
Plant is created by MM Consultant.

IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign sales organization - distribution channel - plant

9. Define Shipping Points
Shipping Point is the Organizational element, which is responsible for shipping the Materials to the Customers.

IMG -> Enterprise Structure -> Definition -> Logistics Execution -> Define, copy, delete, check shipping point

10. Assigning Shipping Point to Plant
This assignment ensures that goods from different Plant can be dispatched from different Shipping Points.

IMG -> Enterprise Structure -> Assignment -> Logistics Execution -> Assign shipping point to plant

Note: Ensure to do the under mentioned configuration also though it is not in Customizing node of Enterprise Structure.

11. Defining Common Distribution Channels for Master Data Use
The purpose of this activity is to define distribution channels which have common master data..

Procedure
Access the activity using one of the following navigation options:

IMG Menu -> Sales and Distribution -> Master Data -> Define Common Distribution Channels
Transaction Code: VOR1

12. Defining Common Divisions for Master DataUse

The purpose of this activity is to define distribution channels which have common master data..

Procedure
Access the activity using one of the following navigation options:

IMG Menu -> Sales and Distribution -> Master Data -> Define Common Division
Transaction Code: VOR2

2007-11-24T01:46:00.000-08:00

Order to Cash Cycle

A customer orders some items from your company by creating a sales order (Tcodes: VA01, VA02, VA03, Tables: VBAK, VBAP etc).

Your company decides to deliver the items ordered by the customer. This is recorded by creating a outbound delivery document (TCodes:VL01N, VL02N, VL03N, Tables: LIKP, LIPS etc).

Once the items are available for sending to the customer, you post goods issue which reduces your inventory and puts the delivery in transit. This will create a material document. You will post goods issue using VL02N but the material document created will be stored in tables MKPF, MSEG.

You will then create shipment document to actually ship the items.

(Tcodes: VT01N, VT02N, VT03N, Tables: VTTK, VTTP etc).

You finally create a sales billing document.

(TCodes: VF01, VF02, VF03, Tables: VBRK, VBRP etc).

This will have a corresponding accounting document created that will be in BKPF, BSEG tables.

When customer pays to your invoice, it will directly hit your AR account in FI.

You will have to remember that these are not a required sequence. Some times, you may configure your system to create a SD invoice as soon as you create a sales order or you may not create a shipping document at all.

This is the position where Functional Consultant would come into picture and study the company's order to cash process and configure the SAP system to do so.

2007-11-24T01:35:00.000-08:00

Differences between Cash Sales and Rush Order

Cash Sales:In this type of order CS, as soon as you save the sales order the delivery is automatically created as same date and billing will also be generated at the same date as soon as you save the delivery document.

In a rush order, the customer picks up the goods immediately, or you deliver them on the same day as when the order was created. When you save the rush order, a delivery is automatically created in the standard system. Billing the rush order takes place as normal, after the delivery.

In the standard system, sales document type RO is saved for rush orders with immediate delivery type LF. Once the goods have been removed from storage, the goods are picked, and goods issue is posted. Once the billing documents are created (for example, in collective processing), invoice papers are printed and sent to the customer.

Rush Order: In this type of Order RO , The delivery will be created as soon as you save the sales order. But you bill the customer later.

In cash sales, you can process an order for when the customer orders the goods, picks them up, and pays for them immediately.

The delivery is processed at the same time as when the order is created and a cash invoice is printed immediately: billing is therefore related to the order, unlike rush and standard orders. Receivables are not created for the customer, as they are for rush and standard orders because the amount in the invoice is immediately posted to a cash account.

In the standard system, sales document type BV (CS) is saved for cash sales with immediate delivery type BV.

When the sales employee creates a cash sale, the system automatically proposes the current date as the date for delivery and billing.

Once the order has been posted, a delivery with type BV is created immediately in the background and the system prints a document that is used as an invoice for the customer.

The invoice papers are controlled with output type RD03, contained in the output determination procedure for order type CS.

2007-11-24T00:48:00.000-08:00

Configuration of Pricing Procedure

In SD, the steps to configure Pricing procedure are as under:

Step 1:

Condition table: If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in SPRO as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Table (select the required fields combination, which will store condition record).

Step 2:

Access Sequence: If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in SPRO as follows:

IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.

Step 3:

Condition Type: If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in SPRO as follows:

IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Type. It is always recommended to copy an existing similar condition type & make the necessary changes. Here we assign Access sequence to Condition type.

Step 4:

a. Pricing Procedure: It is recommended to copy a similar pricing procedure & make the necessary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in SPRO as follows:

IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Maintain Pricing Procedure.

b. Pricing Procedure: After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows:

IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Determine Pricing Procedure.

Step 5:

Condition record: Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc.

2007-11-24T00:36:00.000-08:00

Configuring credit card for the orders

To implement the credit card functionality in SAP, do the following:

Go to transaction VOV8.

Select the required order type and double-click on the same.

Scroll-down the window to find the following fields:

In the highlighted section above, we mention the payment type. In the "Paymt card plan type" select the value "03 (Payment card)" or use F4 functionality to select the same. Here are the F4 values:

In the checking group, enter the value "01(Standard)".

2007-11-24T00:33:00.000-08:00

Differences between Credit Note, Credit Memo and Credit for returns

Credit Note, Credit Memo and Credit for returns are all the same and used interchangeably. In general, Credit Note and Credit Memo are used to pass the credit to the customer if they are charged too much.

"Credit for Returns" is used to return the amount to the customer when the defective products are returned, or a complaint is made about a service performed.

2007-11-23T23:55:00.000-08:00

Extending/Reducing the credit limit for a specific period

Go to transaction OVA8

Select the required record and click on “Change”.

Following screen appears:

As noticed in the above screen, we can maintain the percentage by which the credit limit should be either extended/reduced and also can provide the period for which it is applicable.

Following is the F1 help screenshot of the same:

Following is the screenshot after entering some values in the “Credit Limit Seasonal Factor”:

2007-11-23T23:36:00.000-08:00

Maintaining Shipping instructions

Shipment Instructions are used to instruct the carriers or forwarders or drivers anybody who actually would be shipping your goods from your warehouse to the customer's site. This instructions could be asking the driver to Handle the goods with care or might be instructing him to make sure the delivery is at the customer premises by so and so date and time or once the delivery is handed over to the customer taking a receipt signature from the customer.

Example if you order something from a store , after the goods are shipped to you the driver takes a signature on a receipt note or collects the check or cash form you or takes the inspection done signature, this is the shipping instructions for the driver.

Shipping instructions are maintained in the delivery document itself (Transaction VL01N).

In the delivery document, click on GOTO-->Header-->Text

2007-11-23T22:55:00.000-08:00

MRP: PR to PO Conversion

Go to Transaction SU3 and under Parameters Tab find the Parameter ID "EVO" and check if any value is assigned. If so, make a note of the value.

Now go to transaction SPRO

Click on SAP Reference IMG -> Material Management -> Consumption-Based Planning -> Procurement Proposals --> Define Conversion of Purchase Requisition into Purchase Order (as shown below)

Check for the value we have noted earlier (the value of the parameter EVO in SU3). Select the read and check the check boxes appropriately. We have to select at least one of the check boxes from RefPRs or A/P PR to have all all items copied to PO.

Please use the F1 help for detailed information on the check boxes.

2007-10-10T16:36:00.000-07:00

Integration of SD and HR

Is there any integration between SD module and HR module?

1) Primary Relationship : Enterprise Structure : the highest level of the HR module is Enterprise Structure and this is the base for every module.

While implementing SAP for the companies all the consultants of various modules sit together and identify the elements of enterprise structure from their point of view and form a common code for their various terminlogies.

Let us say Personnela Area ::::::: Human Resource
Plant ::::::: MM and PP
Sales organisation ::::::: SD

Like this for the same area we do address with several names from different SAP Modules.

For this Common Area we take a common code let us say 1000.

So the highest level of organisation after the company code is identified.

Next to this step Our responsibility is to identify "Personnel Sub Areas"

It is a division or Department below the level of personnel area.

From SD module below the sales organisation distibution channela and divisions will come. Also the sales Areas . these are all assigned to the Sales organisation. And we know sales organisation has to be assigned to the Company Code.

Meas From HR Personnel area = Sales Org in SD
Personnel Subar = Distibution channel , Division

To identify which is the common terminology for personnel subarea, we need to identify the reporting structure of the company and its accountability at each level .

THIS APPEARS TO SIMPLE BUT SO COMPLEX.

Like this maintaining the relationship at enterprise structure level shuold be done

2) Seconday Relationship (Indirect Relationships):

Sales areas are assigned to another sales areas. Here many to many relationships are maintained rather than many to one ( many Sales orgs to one company code) of primany relationships.

Here we should be very keen From H R point of view to identify personnel sub areas.

At the same time we should keep in mind the functionality of cost center also while framing the structure .

3) Employee relationships :

HR Point of view:

Once we identify the employee groups in the company like permanent, contracts, temporary , trainee etc., we do focus on Employee Sub Groups.

SD Point of view :

If the employee is at TRAINEE or PERMANENT or TEMPORARY has to be decided and accordingly should be assigned on recruitment at org assignemnt infotype 0001.

We aslo know that infotype 0900 may also be initiated for maintaining the master data of employee at PA 30 to assign sales
organisation,Sales Office, Sales Groups to each employee.

4) Recruitment : We at HR have to identify the position and declare it as vacancy then we can recruit as per our procedure as every body knows.

Other wise go to the transcation code PAL1 and creat sales representative and assign him to respective org div through 0001 infotype. PAL3,PAL4 also may be useful.

Like this at enterprise structure and employee structure HR and SD share common ideas.

Pricing-16

2007-10-04T11:41:00.000-07:00

Add a Field To New Condition Table in Pricing

Add a field to a new condition table in Pricing (Condition Technique):-

I will explain you the process with below example...Please follow steps in below sequence-

Try to add the filed from the field catalog. In case the required combination field is not there, you can add the field through the following process to filed catalog and create the condition table. It is most common that one or other time we need to use this function while configuring multi tasking & complex Pricing Architecture.

Here I'm giving a simple guide to add fields to the Pricing Field Catalogues:

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

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

Condition access, field catalog, allowed fields, KOMG, KOMK, KOMP, KOMPAZ, KOMKAZ, PSTYV are the other terms which we need to know about, to add Fields.

Reason and Prerequisites:
For technical reasons, field PSTYV was included in structure KOMP, however, not in structure KOMG ('Allowed Fields for Condition Structures').

Proceed as follows:

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

2. Call up structure KOMPAZ in the ABAP Dictionary (Transaction SE11) in the change mode and make the following entry:
Component Component type:
ZZPSTYV ZZPSTYV
Save, check and activate the change you made.

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

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

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

6. Supply the new field you defined by including the following source code line in USEREXIT_PRICING_PREPARE_TKOMP:
MOVE xxxx-PSTYV TO TKOMP-ZZPSTYV.
In order processing you find the user exit in Include MV45AFZZ, and in billing document processing you find it in Include RV60AFZZ.

Consider that you can also use this note as a help if you want to use other customer-specific fields as key fields in a condition table.

For header fields, use structure KOMKAZ instead of structure KOMPAZ and
USEREXIT_PRICING_PREPARE_TKOMK instead of
USEREXIT_PRICING_PREPARE_TKOMP.

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

Pricing-15

2007-10-04T11:28:00.000-07:00

SD Questions About Pricing Condition

The Most Important Tips in Pricing For SAP SD Module to crack interviews...

Whenever we define our pricing procedures, we remain least interested in creating our own Condition Types,Condition
Tables & Access Sequences. What we do is, we just define our own pricing procedures by using the existing condition types (i.e: PR00, K004, K007, KA02, KF00 etc.) & then assign that Pricing Procedure with " Sales Area, Document Pricing Procedure & Customer Pricing Procedure " .

After that we put the values against each Condition Types, mentioned in our Pricing Procedure by using the T-Code "VK11". But we also need to know about the Condition Tables, Condition Types & Access Sequence Creation. So for that purpose we have to use the following T-Codes respectively : "V/05", "V/06" & "V/07". Now it will become easy to create the same.

Also to inform that, using T-Codes is more smarter than following paths through IMG screen.

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

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

Difference between VK11 and VK31 - if you go through the menu path you will get the vk 31 as condition record from the tamplets whereas vk11 as simple condition record. In VK11 you can store condition record for more than one condition type.

This means you can have same condition record for different condition types.This feature is given to enhance the system's performane and not to create the duplcation of the work for each condition type.

Again system is not allowing to store the record in the vk31 for the condition type pr00 and access sequence pr02.This is because if you see this ac seq cointains two accessses 20 and 30 having the same table no.But you see there is the difference between the technical view of it for transfering the data from document field and condition field,so you can not maintain the data at VK31.

What is the difference between Header condition and Item condition? I know item condition applies to each item in a sales document. Header condition can only be applied to an entire document.

Difference between header and item condition - as YOU CORRECTLY SAID HEADER CONDITION IS APPLICABLE FOR THE WHOLE DOCUMENT where as item is for item.

Ex-Say fright is dependent on the total weight of all the items in the documents then header condition adds on weights of all items and calculates the record accordingly.
You have two different types of the header conditions.

a) In one you can duplicate the same value throughout the document for each item.Say discount 2% at header level which is also applicable to all the items

b)Second is the accumulation of the values of all the item at the header level,as earlier explained for the weight/fright.

These differenes are controlled through the indicator of group condition in the cond.type configuration.

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

Disallowing Condition Types - How I can accomplish the following:

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

You can modify condition type from customizing;

Sales and Distribution->Basic Functions->Pricing->Pricing Control->Define Condition Types->Maintain Condition Types

Change condition type ZOBP's plus/minus indicator to "A" which means only positive is allowed.

In pricing procedure there are column such as requirement, sub total altclty, altbv, accurals. What are these and where we calculate all these values which we put.

1. Requirement: Denoted by nos and maintained in VOFM, this is a condition required for a particular condition type to be executed.

Eg. PR00: req 2 ie item relevant for pricing
VPRS/EKO1: req 4 ie cost
Rebate BAO1 Req 24/Req 25 etc

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

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

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

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

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

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

Pricing-14

2007-10-04T11:22:00.000-07:00

Steps to Create Commission for Agent

For creating commission agent, you have to follow below steps.

1) Establish Partner Functions for the Commissionee(s)

Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PARTNER DETERMINATION ->; DEFINE PARTNER FUNCTIONS
Transaction Code: VOPA

2) Assign the Partner Functions to Partner Procedures

Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PARTNER DETERMINATION ->; DEFINE PARTNER FUNCTIONS
Transaction Code: VOPA

3) Create a Partner Procedure for the Commissionees

Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PARTNER DETERMINATION ->; DEFINE PARTNER FUNCTIONS
Transaction Code: VOPA

4) Create New Customer Account Group(s) for Commission Agents

Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; LOGISTICS GENERAL ->; LOGISTICS BASIC DATA: BUSINESS PARTNERS ->; CUSTOMERS ->; CONTROL ->; DEFINE ACCOUNT GROUPS AND FIELD SELECTION FOR CUSTOMER
Transaction Code: OVT0

5) Assign the Partner Functions to the Customer Account Group(s)

Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PARTNER DETERMINATION ->; DEFINE PARTNER FUNCTIONS ->; GOTO ->; PARTNER FUNCTIONS ->; ENVIRONMENT ->; ACCOUNT GROUP ASSIGNMENT
Transaction Code: VOPA

6) Assign the Partner Functions to the Partner Procedure for the Sales Document Header

Menu Path: Tools ->; Business Engineer ->; Customizing ->; Sales and Distribution ->; Basic Functions ->; Partner Determination ->; Define Partner Functions
Transaction Code: VOPA

7) Assign the Partner Functions to the Partner Procedure for the Sales Document Item (OPTIONAL)

Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PARTNER DETERMINATION ->; DEFINE PARTNER FUNCTIONS
Transaction Code: VOPA

8) Edit the Pricing Communication Structure (KOMKAZ) to Hold the New Functions (Client Independent)

Menu Path: Menu Path: TOOLS ->; ABAP WORKBENCH ->; DEVELOPMENT ->; DICTIONARY
Transaction Code: SE11

9) Edit MV45AFZZ – userexit_pricing_prepare_tkomk (Client Independent)

Menu Path: TOOLS ->; ABAP WORKBENCH ->; DEVELOPMENT ->; ABAP EDITOR
Transaction Code: SE38

10) Edit RV60AFZZ - userexit_pricing_prepare_tkomk (Client Independent)

Menu Path: TOOLS ->; ABAP WORKBENCH ->; DEVELOPMENT ->; ABAP EDITOR
Transaction Code: SE38

11) Edit MV45AFZB - userexit_new_pricing_vbkd changing new_pricing (Client Independent)

Menu Path: TOOLS ->; ABAP WORKBENCH ->; DEVELOPMENT ->; ABAP EDITOR
Transaction Code: SE38

The following code should be inserted into program MV45AFZZ to allow the system to re-execute pricing if the user makes a change to the relevant partner function (alteration, addition, deletion).

12) Add the KOMKAZ Fields to the Pricing Field Catalog (Client Independent)

Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PRICING ->; PRICING CONTROL ->; DEFINE ACCESS SEQUENCES ->; MAINTAIN ACCESS SEQUENCES
Transaction Code: OV24

13) Create Condition Tables (Client Independent)

14) Create an access sequence containing the new tables (Client Independent)

15) Create a new condition type

Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PRICING ->; PRICING CONTROL ->; DEFINE CONDITION TYPES ->; MAINTAIN CONDITION TYPES
Transaction Code: V/06

16) Add the Condition Type to the Pricing Procedure

Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PRICING ->; PRICING CONTROL ->; DEFINE AND ASSIGN PRICING PROCEDURES ->; MAINTAIN PRICING PROCEDURES
Transaction Code: V/08

17) Create Commsission Report ZZCOMMISSION (Client Independent)

Menu Path: TOOLS ->; ABAP WORKBENCH ->; DEVELOPMENT ->; ABAP EDITOR
Transaction Code: SE38

Pricing-13

2007-10-04T11:11:00.000-07:00

Customer discounts on effort only

We have a requirement of giving a discount to customer based on the total amount invoiced so far (across financial years). Where do we set this up? We have seen so far the discounts are calculated based on the value of the current invoice.

The discount should be on a graduated scale basis for example

0 - 100000 No discount
100000 - 200000 5%
200000 - and above 10%
This means that discount would only start after the customer's net sale value crosses 100000.

For example, if the customer has been billed for 99000 and the current invoice is for 3000, a discount of 5% should be given on 2000 i.e. 100. Another complication is that, the discount is not based on the total amount billed so far, but only on the effort billed and not on reimbursements (like airfares, living expenses, visa charges, beeper charges etc).

The discount applies only to the effort and not to the reimbursements. In the above example (invoice of 3000) say the effort billed is only 1500, the rest being reimbursements. The discount is only on the 500. (the rest being taken up by the lower limit for eligibility of 100000)

For example the customer might have been billed say 150000 so far but actual effort billed might be only 90000, the rest being reimbursements of actual costs and hence the customer is not eligible for the discount.

solution1:

The solution for this is Using rebate condition types and suitable condition records.

Of this to handle your first problem that is the rebate has to be applied only on the "effort" you have to set up a line in the pricing procedure which gives the rebate basis i.e the value to be used for rebate cond types.

This I believe solves your problem of rebate only on effort.

Your second problem i.e the discount should start getting applied automatically when it reaches the first scale for which the values span few financial years. This I am not really sure whether it can be made possible in the invoice itself. But a work around is not giving the discount directly in the invoice but settling it against the rebate agreements by Credit notes periodically.

solution2:

Arent we looking at rebate agreeement. That appears to be a straightaway solution to your problem. You activate the sales organization and the payer for that

solution3:

I am in SAP R/3 rel.30F.
We have 2 options to meet your requirement.

1. Using scale in condition type ( tcode V/06 ), choose scale basis G.Scale based on a formula ( be: your based amount is invoice ). Define scale formula. You need ABAPER to define it.

2. Using routine in Alt.calc.type ( tcode V/08 , Maintain Pricing Procedure ). Here, you also need ABAPER to create routine.

Pricing-12

2007-10-04T11:02:00.000-07:00

Make Material Master Price of a material as sales price automatically

The first method is not to set the pricing condition VPRS as statistical.

Simply remove PR00 and it will work fine if you always use VPRS as your pricing base inside the pricing procedure.

VPRS will reads both prices based on the price control in the material master.

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

It is this simple if you do not have any other "Prices" in the price procedure.

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

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

This is how it goes :-

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

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

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

The pricing procedure than looks like that:

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

Pricing-11

2007-10-04T10:58:00.000-07:00

Mass Update of condition pricing

You can update the condition pricing for a range of sales order.

For e.g. if you create sales order for 15 months or so, and at the beginning of each year, you have to update the prices for lots of sales orders.

Other than using VA02 and make an Update of the conditions at item level which is a big work because you will have lots of open sales order after so many months.

Use VA05, select your Orders and on the result screen :-

click Edit- > Mass Change -> New Pricing (menu).

if you don't want to do that Online, write your own abap report and use Function SD_BULK_CHANGE (check where-Used at SE37, Trace VA05 on how to fill the parameters, Function MPRF => New Pricing)

Pricing-10

2007-10-04T10:49:00.000-07:00

Report to Check the Entered Pricing Condition Price

Which is the best transaction code to check the Pricing condition price entered in "VK11"?

Other than "VK13", to display the price, you can use V/LD - Execute Pricing Report to check the prices entered into the Pricing Master.

Normally Pricing Report - "07 Cust.-specific Prices with Scale Display" will do.

Other Pricing Reports you can tried are these:.

---------------------------------------------------------------------------
|LR|Report title                                                          |
-- ------------------------------------------------------------------------
|01|Comparison of Price Lists Without Scale Display                       |
|02|Comparison of Price Groups Without Scale Display                      |
|03|Incoterms with Scale Display                                          |
|04|Incoterms Without Scale Display                                       |
|05|Price List Types Without Scale Display                                |
|06|Price List Types with Scale Display                                   |
|07|Cust.-specific Prices with Scale Display                              |
|08|Cust.-specific Prices W/out Scale Display                             |
|09|Material List/Material Pricing Group with Scale Display               |
|10|List Mat./Mat.Pricing Groups Without Scale Display                    |
|11|Price Groups With Scale Display                                       |
|14|Taxes                                                                 |
|15|Material Price                                                        |
|16|Individual Prices                                                     |
|17|Discounts and Surcharges by Customer                                  |
|18|Discounts and Surcharges by Material                                  |
|19|Discounts and Surcharges by Price Group                               |
|20|Discounts and Surcharges by Material Group                            |
|21|Discounts and Surcharges by Customer/Material                         |
|22|Discounts and Surcharges by Customer/Material Group                   |
|23|Discounts and Surcharges by Price Group/Material                      |
|24|Discounts and Surcharges by Price Group/Material Group                |
|25|VAT/ATX1                                                              |
|26|Canada/USA                                                            |
|27|I.E.P.S Mexico                                                        |
|28|Conditions by Customer                                                |
|30|Conditions by Customer Hierarchy                                      |
|31|Price List with Release Status                                        |
|AC|                                                                      |
|AD|                                                                      |
---------------------------------------------------------------------------

Pricing-9

2007-10-04T10:41:00.000-07:00

Pricing date based on delivery date

Used transaction VOV8.

This configuration is by order type.

There is a field called proposal for pricing date.

There you can select pricing date as requested delivery date.

A - Proposed pricing date based on the requested dlv.date (Header)

This control is set at the document level as oppose to the condition type level (PR00).

That means your other condition types such as surcharges and discounts are also determined using the requested delivery date.

If your requirement is for PR00 to alone to be priced at delivery date then this will not work.

How pricing date is determine in the sales order and billing document? Where is the setting?

The pricing date is proposed based on the setting you make in the Sales document configuration. ( T code : VOV8)
You have a field" Prop.f.pricing date " in the Requested delivery date / pricing date / purchase order date segment.

Then you can choose the follwoing options:

Blank - Indicates the current date as the pricing date

A - Indicates the date based on the requested delivery date

B - Indicates the date based on the order validity start from date

And the pricing in the billing document is copied from thte sales order / Delivery document..

It again depends on the setting u have in the copy control from order - billng or delivery - billing.
In the copy control, in the item settings you have two fields relavant for this.

One is pricing source and the other is pricing type.

The pricing sources are generally the order. But if you want you can change it to other values mentioned in the drop down,
but this values have no effect if the pricing type is B.

Any other value other than B in the pricing type will take the reference document price mentioned in the pricing source field.
but for the pricing type B. The new price is determined in the billing order.

Pricing-8

2007-10-04T10:37:00.000-07:00

Determine Sales Price with Shipping Point

You are trying to use shipping point as a key field (with sales org. distribution channel and ship-to party together) to determine the sales price. You created a condition table with the above key fields, and maintained the relevant setting (access sequence, condition type and pricing procedure).

There is an error message in the sales order pricing analysis ("access not made" in the shipping point field).
In the access sequence, you found that the shipping point field's document structure is KOMK.

Can you put to item level field in the condition table and access sequence?

Structure KOMK refers to header of the sales order, but shipping point of course is on item level.

You'll have to do some settings to reach your goal, it is possible.

Step 1
Append structure KOMP. Do this by changing through SE11 the table KOMPAZ.
This is the include for structure KOMP.
Add a component e.g. ZZVSTEL with component type VSTEL.
Save, activate.
If you want to make more points, assign search help H_TVST to the component.
Ask a programmer if you don't understand this part.

Step 2
Change user exit MV45AFZZ. Say there that field ZVSTEL should be filled with information from your shipping point.
Do this under part FORM USEREXIT_PRICING_PREPARE_TKOMP.
The coding should be like tkomp-zzvstel = vbap-vstel.
Save, generate.

Step 3
Make a new table as you did before, but first maintain your new field in Condition: allowed fields.
When you create your new table you will see you have two shipping points.
With the button technical view you can check which one ZZVSTEL or VSTEL.

Step 4
Finish with the steps you did before. That was ok.

Now, you will see in your sales order that the shipping point is filled with information.

Pricing-7

2007-10-04T10:30:00.000-07:00

Quantity Based Discounts in Bulk Quantities Sales

You're looking to implement quantity based discounts in 4.6c. You are trying to sell items in specific bulk quantities, and only give the discount for specific quantity intervals.

For example, if a customer orders 1 piece, 2 pieces, 3, etc. of part ABC, the price is $100.

If the customer orders 10 pieces of part ABC, the price is $50.

However, this is not only a standard minimum quantity discount. If the customer tries to order 11 pieces, 12, 13, etc. it should return $100 again.

The only values for which $50 should apply are 10, 20, 30, etc. - multiples of the bulk quantity 10.

You have discussed changing your part number to reflect a bulk qty of 10, however you have in house consumption that is allowed to consume only 1 part at a time. You would vastly prefer to keep one part number that you order from the supplier, consume internally and ship externally.

You are fairly certain there is basic functionality that covers this, but you're just not sure where to start.

Taking your requirements literally. Standard SAP scale pricing will not do it in that you only want the reduced price to come into effect when the order quantity is multiple of some bulk factor.

It is agreed with that creating a separate material number is not a good idea.

You can try this :-

1. Define/Select a UOM for selling in bulk (i.e. cas, pallet, box whatever)
2. Maintain UOM conversion between your base UOM and this new UOM
3. Configure you bulk pricing condition type by usual means (it should be a base price rather than discount).
4. Place this new bulk price behind your normal "PR00" price in the pricing procedure
5. Create a new condition base value routine via VOFM where you check XKWERT to see if it is a whole number. If it is not then set XKWERT to zero.
6. Assign this new routine to your bulk price condition in your pricing procedure in ALT condition base value column.
7. Maintain bulk price conditon record in the Bulk UOM.

That should do it.

Pricing-6

2007-10-03T15:05:00.000-07:00

Re-pricing in a Quotation

How can I, or am I able to find anything on a way of RE-Pricing be done in a QUOTATION?

You can always 'Update" pricing manually in a quotation the same way you do in a sales order, either in create or change modes. Menu path Edit --> New Pricing or press the 'Update pricing' button on the item conditions tab.

If you are asking how to reprice a quotation when it converts into a sales order, that can be done with the copy controls of the Item Category. IMG: Sales & Dist --> Sales --> --> Maintain Copy Control for Sales Docs --> Sales Doc to Sales Doc (transaction vtaa). Just choose the combination of documents and the respective item category. The field you need to be concerned with is "Pricing type".

However, from a business process perspective it makes absolutely NO sense to reprice a quotation when converting to a sales order. After all, the entire point of using quotations is to firm up details like pricing before creating the sales order.

Pricing-5

2007-10-03T15:02:00.000-07:00

What is "alt cal type" & "alt base value" & "Requirement field" in the Pricing Procedure

Can any one explain exactly what is "alt cal type" & "alt base value" and also " Requirement field" in the pricing procedure?

The alternate base value is used as the calculation basis only, while the alternate calculation is used to modify the final value.

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

The alternate base value could say, "don't use $100 as the basis -- use the original price PR00 only, which was $90." Then, the final value would be $100 + (10% of $90) = $109.

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

Put them both together, and you could end up with $100 + (20% of $90) = $118.

Now once again,

Alternative Calculation Type:

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

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

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

Alternative Condition Base value :

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

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

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

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

Pricing-4

2007-10-03T14:57:00.000-07:00

Creating New Pricing Procedure

What is the transaction code for creating new pricing procedure and how to attach it to specific plant?

You create PP in spro > Sales and Distribution > Basic Functions > Pricing > Pricing Control > Define and Assign Pricing Procedures > Maintain Pricing Procedures

You can't attach PP to specific plant. Pricing Procedure is determined thru trx OVKK. The defining parameters for pricing procedure determination are:

1. SalesOrg
2. Distribution Channel
3. Division
4. Document Procedure (defined in Sales doc\Billing doc maintenance)
5. Pricing procedure assigned to customer (defined in customer master)

Hope this helps.

Reg pricing procedure.

1. Use transaction code v/07 to create a access sequence and assign tables based on which you want to carry on pricing as accesses.

2. Use transaction code v/06 to define condition type. It can be for base price, discount, freight etc., (Do assign relevant access sequence)

3. Use transaction code v/08 to define pricing procedure.

4. Assign this to your relevant sales area+ dpp+cupp.

While specifying requirement, we can give reqt no.22 which specifies that plant has to be set. This is generally done for output taxes since output taxes depend upon the delivering plant. But directly there is no assignment between plant and pricing procedure.

Hope this helps,

Pricing-3

2007-10-03T14:45:00.000-07:00

Hiding Price Condition Types on a Sales Document

Up to now you, you still cannot exclude certain condition types and subtotal lines from being processed or displayed in the condition screen by restricting the authorizations.

You have to implement SAP Note No. 105621 - Authorization check for the condition screen

Pricing-2

2007-10-03T14:44:00.000-07:00

Accumulate the amount of condition types in accounting document

To accumulate the amount of condition types in accounting document without affecting the pricing display in billing document.

As an illustration :-

ZPXX 3500
ZDXX 1000-
ZWXX 500-

(all condition types are shown separately in pricing view)

Journal:
Dr Vendor 2000
Cr Sales 2000 (ZPXX - ZDXX - ZWXX)

One way to do it is :-

Mark the condition types you want to group as statistical and remove the account assignment key.

Create a subtotal in your pricing procedure that will add them together and put in the account assignment key for it. This way the individual components will still display on your pricing screen but FI will only get one posting.

Pricing-1

2007-10-03T14:40:00.000-07:00

Difference between Condition Type

Please explain the difference between Ek01 ( Actual Cost) and EK02 Calculated Cost.

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

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

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

Please note the following points :

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

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

I have a customer who is being offered two discounts ie k007 and k005, now I want to exclude k007 for the next 2 orders or so? I have set the exclusion indicator for the condition type,but still the condition is being accepted when I create a sales order. Am I missing something, how do I do it?

I think u need to change the validity of the condition record for the condition type K007 defining it not valid for that particular 2 months. And also the settings of the Requirements as it is correct that it overrules the exclusion.

Sheduling

2007-10-03T14:33:00.000-07:00

Backward and Forward Scheduling

Backward scheduling is the calculation of deadline dates: the arrival time at the customer site is calculated as the earliest possible goods receipt time at the customers unloading point on the requested delivery date. All four of the delivery and transportation scheduling lead times are subtracted from the customer's requested delivery date to determine if this date can be met.

The transit time, loading time, and pick/pack time are subtracted from the customer’s requested delivery date to calculate the required material availability date.

The system calculates backward scheduling as follows:

Requested delivery date minus transit time = Goods issue date
Goods issue date minus loading time = Loading date
Loading date minus transportation lead time = Transportation scheduling date
Loading date minus pick/pack time = Material availability date

By default, the system will calculate delivery dates the closest day, taking into consideration the working days of the shipping point and a rounding profile. In this case the system assumes a 24 hour work day and lead times can be entered in days up to 2 decimal points. This is referred to as daily scheduling.

Precise scheduling calculated down to the day, hour and minute is supported. This allows the scheduling of a delivery within a single day. It is activated by maintaining the working hours for a particular shipping point.

Backward scheduling is always carried out first. If the material availability date or transportation scheduling date is calculated to be in the past, the system must then use forward scheduling.

Forward scheduling is also done if no product is available on the material availability date calculated by backward scheduling. The system does an availability check to determine the first possible date when product will be available. This new material availability date forms the starting point for scheduling the remaining activities. The loading time, pick/pack time, transit time, and transportation lead time are added to the new material availability date to calculate the confirmed delivery date.

Multiple Materials in Material Determination

2007-10-03T14:30:00.000-07:00

Creating Multiple Materials in Material Determination

Material Determination is used to swap one material for another.It is possible to get a list of materials for substituiton,but remember you can substitue only one material from the list.

This can be done through substituiton reason T Code [OVRQ]
See the substitution reason number for Manual Material Selection
- check the Entry box
- check the Warning box
- select A for Stategy
- save.

Go To VB11 to create Material Determination (taking into consideration that all the previous steps for material determiantion i.e. maintaining condition types,maintaining procedures for material determination and assigning procedures to sales doc. types have been done)

Create one material determination,dont forget to give the Subst reason on top and also on the line.

Click the Variants Icon on top left-Sreen opens

Specify different materials you want to swap with the material you have enterd

Note that the subst reason is already copied on the screen

Remember materials should be of the same sales area,atleast Divisions should be same.

Material Determination based on Availability check

2007-10-03T14:27:00.000-07:00

SD material Determination based on availability check

For SD material Determination you can create a Substitution reason and on the Strategy field, the following info. is available:

Product selection in the background is performed on the basis of the availability check.

We want to have the material determination only in case on material shortage. We expect the Substitution reason to give us this functionallity. It does not hovever take the availabilty into account before substitution.

We thought the worse case is to create a ABAP which is linked to the "requirement" field in the Procedure (OV13).

Has anyone had the same requirement? Is this a bug or just incorrectly documented?

I also encountered this abnormally recently using material determination. In order to combat the problem, the first product substitution should be for the original material. I've illustrated this below:

Original Product: ABC
Substitutes: DEF, XYZ

In order to perform product substitution ONLY in the case of ATP failure for product ABC, structure the Material Determination record as follows:

Material Entered:

ABC Substitutes:

ABC
DEF
XYZ

There seems to be a devaition at availability check and or on a conceptual note still.

Availability check can be configured both at requiremnt class and at the schedule line categories level.

Whilst the availabilty check at the requirement class level via global and mandatory configuration the schedule line catgry availability check deals with the order.

It is mandatory that the reqmnt class is flagged off for avlblty check and the schdelu line cat need not be.

The following are the mandatory for Availability check to happen--

1. Must be swithced on at the requirment class level and at the schedule line level.

2. Reqmnt type must exist by which a requiremnt class can be found

3. There must exist a plant and is defined

4.Checking group must be defined in Material Master records(it controls whthr the system is to create individual or collective reqmnt)

A combination of checking gropup and checking rule will determine the scope of availbaility check.

AvailabilityCheck

2007-10-03T14:24:00.000-07:00

Availability Check on Quotation

SAP standard does not do an availability check on the quotation, as it is not a definite order, usually just a pricing quote.

When it is converted to an order, the first availability check is carried out, as well as credit checks. The system will check stock in the plant, plus what is contained in the availability checking rule (scope of check)

eg: can add POs for replenishment, purchase reqs, different planned orders, and subtract sales orders, deliveries etc already created against that material in that plant (and possibly Storage location).

If there is enough stock in the plant/SLoc, the system will give you a confirmed date, or give you a date based on the production time or purchasing time from the material master. The date the system proposes is based on the customer's requested delivery date.

SAP first backward schedules looking at the required delivery date, less transportation time, less transportation lead time, less pick and pack time, less production/purchase time if applicable.

If the date it calculates is equal or later than today’s date, then it will confirm the customer’s required date. If it falls in the past, SAP will then forward schedule for today’s date, plus the times listed above to get the date when the customer can actually have it.

ATP is the single most complex part of the SD module, depending upon how PP and MRP is set up.

MRP works semi-separately, depending on how it is set up. Basically, MRP looks at the demand on the plant, and if it the stock does not meet expected sales orders and deliveries, it will create a purchase requisition (outside purchase) or requirement or planned order (for production) to cover the shortfall. When MRP is started, it will turn the PR into a PO or the requirement into a production order.

BILLING-8

2007-09-09T13:05:00.000-07:00

Billing Spilt by Item Category

Is it possible to split invoice Item category wise. I mean If in sales order there is TAN and TANN then the invoice should split,is it possible?

Yes, it is possible. Create a modification of copy control routine for billing and use VBAP-PSTYV as an additional split criteria there.

Thank you for your reply. Can you please tell me the exact steps what should I add under that(additional split criteria).

In trx VTFA (if your billing is sales order based) choose your billing type and SO type, there select your item categories and there select the field VBRK/VBRP data. In that field you will see the currently used routine. With the help of your ABAP guy create a copy of that routine under a different number and add your lines of code. Let's say you use routine 001.

FORM DATEN_KOPIEREN_001.

* Header data
* VBRK-xxxxx = ............
* Item data
* VBRP-xxxxx = ............
* Additional split criteria

DATA: BEGIN OF ZUK,
MODUL(3) VALUE '001',
VTWEG LIKE VBAK-VTWEG,
SPART LIKE VBAK-SPART,
END OF ZUK.

ZUK-SPART = VBAK-SPART.
ZUK-VTWEG = VBAK-VTWEG.
VBRK-ZUKRI = ZUK.

ENDFORM.

This is how it should look after modification:

* Header data
* VBRK-xxxxx = ............
* Item data
* VBRP-xxxxx = ............
* Additional split criteria

DATA: BEGIN OF ZUK,
MODUL(3) VALUE '001',
VTWEG LIKE VBAK-VTWEG,
SPART LIKE VBAK-SPART,
PSTYV LIKE VBAP-PSTYV, <- New line END OF ZUK.

ZUK-SPART = VBAK-SPART.
ZUK-VTWEG = VBAK-VTWEG.
ZUK-PSTYV = VBAP-PSTYV. <- New line VBRK-ZUKRI = ZUK.

ENDFORM.

After this routine is created and activated place it as the default copy control routine instead of the old ones.

BILLING-7

2007-09-09T13:01:00.000-07:00

SAP Billing - Combine Billing for deliveries with different date

When using transaction VF04 or Billing (background), the date of the billing document (e.g. the current date) must be entered (In VF04 : settings, default data.)

In VF06 or background: variant with parametrization) to avoid an unwanted split due to the billing date.

This OSS notes is very helpful :-

11162 - Invoice split criteria in billing document

36832 - Invoice split in fields from the sales order

BILLING-6

2007-09-09T11:40:00.000-07:00


Billing Plan for Milestone Billing

Milestone billing means distributing the total amount to be billed over multiple billing
dates in the billing plan.

As each milestone is successfully reached, the customer is billed either a percentage of
the entire project cost or simply a pre-defined amount.

During sales order processing, the system determines from the item category whether a
billing plan is required and, if so, which type of plan

The type of billing plan that is determined at this point is set up in Customizing and
cannot be changed in the sales document.

Billing plans for periodic billing and milestone billing plans for project-related milestone
billing have different overview screens so that you can enter data relevant to your
processing.

For example, for milestone billing, you must be able to enter data to identify the
individual milestones.

IMG configuration requires :-

1. Maintain billing plan types for milestone billing in OVBO.

2. Define date description in SM30 - V_TVTB.

3. Maintain Date Category for Billing Plan Type IN OVBJ.

4. Allocate date category in SM30 - V_TFPLA_TY.

5. Maintain date proposal for Billing Plan Type in OVBM.

6. Assign Billing Plan Type to Sales Documents Type in OVBP.

7. Assign Billing Plan Type to Item Categories in OVBR.

8. Define rules for determining the date in OVBS.

Milestone billing is typically used for billing projects, such as plant engineering and
construction projects. Such projects often include a series of milestones that mark the
completion of different stages of the work. In the SAP R/3 System, milestones are defined
in a network along with planned and actual dates for the completion of work. The milestones
are also assigned to the billing dates in the billing plan.

Each milestone-related billing date is blocked for processing until the Project System
confirms that the milestone is completed.

Delivery-relevant order items for which a milestone billing plan applies are billed on the
basis of the requested delivery quantity and not on the total of the confirmed quantities.

The connection between the project and the sales document item is made in the individual
schedule lines of the item. Each schedule item can be assigned to a network in a project.

To display the project-related data for a schedule line, proceed as follows:

In one of the overview screens of the sales document, select

1. Item -> Schedule lines.
2. Mark the schedule line and select Procurement details.

The following figure shows an example of milestone billing where only the Contract have
been billed :

Order Item Turbine 100,000

Billing Plan

Billing date Description % Value Billing Block Milestone Billing Status
01-10-94 Contract 10 10,000 - x x
01-03-95 Assembly 30 30,000 x x
01-04-95 Maintenance 30 30,000 x x
01-05-95 Acceptance 30 30,000 x x
01-06-95 Final invoice .. .. x

Network/Activities

Milestone Estimate Actual
Assembly 01-03-95 01-03-95
Maintenance 01-04-95
Acceptance 01-05-95

For each billing date in a milestone billing plan, you can specify whether the billing
date is:

1. fixed
2. always updated with the actual date of the milestone
3. updated with the actual date of the milestone, if the date is earlier than the
planned billing date for the date

BILLING-5

2007-09-09T11:23:00.000-07:00

Billing Block will not worked if you did not assign it

Define the possible block indicators in SM30 - V_TVFS

and

allocate them to the billing types concerned in SM30 - V_TVFSP.

Your Billing Block will not worked if you did not assigned it to the desired billing types.

You can auto block by :-

1. sales document type in transaction VOV8, fields Billing Block,

2. item categories in SM30 - V_TVAP, by filling the fields Billing Block.

BILLING-4

2007-09-09T11:16:00.000-07:00

Steps for creating a new or changing an existing Billing Document Types

Create/Change your Billing types configuration in VOFA.

Some of the IMG stuff are :-

1) To block automatic transfer of the billing document to accounting, mark the field.
Indicates whether the system blocks automatic transfer of the billing document to
accounting.

During document processing, you can manually transfer blocked billing documents to
accounting by selecting:

Billing -> Change -> Release accounting

2) Account determination procedure

3) Output determination procedure etc. ...

After customizing, use transaction VCHECKVOFA to check your configuration :-

1) Proforma billing types: If it is a proforma billing type, (VBTYP = U), the field must
be blank and the account determination procedure must be empty.

2) Cancellation billing document types: : A check is made to see if the cancellation
billing document type has the right VBTYP. An F2 invoice, for example, (VBTYP 'M')
can only be canceled with billing type S1 with VBTYP 'N' . A billing type with
VBTYP '5' can only be canceled with the VBTYP '6' and vice versa.

3) Cancellation billing document type partner functions A check is made to see if the
cancellation billing document type partner functions are empty or if those that
correspond to the billing type used are empty.

Next, make sure that you maintain the copy control for the Billing Types:

Sales documents in VTFA

Target Source
e.g. F1 - Invoice OR - Standard Sales Order
F1 - Invoice ZOR - Your Sales Order

Billing documents in VTFF
e.g. G2 - Debit Memo F1 - Invoice
G2 - Debit Memo F2 - Invoice

Deliveries in VTFL
e.g. F1 - Invoice LF - Delivery
F1 - Invoice ZOR - Your Delivery

Usually for copy control, you let the rest of the settings remains as SAP defaults.

You only assign the new Billing Document Types.

After that use transaction VCHECKTVCPF to check your Copy control customizing.

BILLING-3

2007-09-09T10:55:00.000-07:00

Condition Exclusion which will be determined in the billing document

The system can exclude conditions so that they are not taken into account during pricing.

For example:

Material 4711 costs 150 USD. Some customers receive a discount of 10 USD per 100 pieces.

However, a specific customer can buy the material for 100 USD. Since this is a particularly good price, the customer should not also have a discount of 10 USD per 100 pieces. Therefore, this discount is to be excluded from pricing.

To create a condition exclusion procedure which will be determined in the billing document.

Assign the procedure to the pricing schema, and maintain copy control so that pricing is not copied from Sales Order.

To achieve this, copy the standard pricing to a ZXXXX Pricing.

Define new document pricing procedure in SM30 - V_TVKV for billing.

Assign new document pricing procedures to billing types in SM30 - V_TVFK_PR

Define the Condition Exclusion Groups in OV31.

Assign the Condition type for the Condition Exclusion Groups in OV32.

Assign the Billing Pricing Procedure in VOK8 for the Condition Exclusion Groups.

When billing document is being created just enter manually your new price and the pricing program logic will include only the higher price one, excluding the rest that are lower price.

BILLING-1

2007-09-09T10:53:00.000-07:00

Billing cannot be Release to Accounting

This SAP message will appear if the system is unable to find the G/L codes match from the configuration in transaction VKOA

No account is specified in item 0000001001
Message no. F5 670

Diagnosis

No account was specified for account type "S" in item "0000001001" of the FI/CO document.

System Response

The Financial Accounting program cannot process the document.

Procedure

A system error has probably occurred in the application you called up. Check the data transferred to item "0000001001" of the FI/CO document.

Assuming that one of the key combination is Account Assignment Group, you will have to check whether have the Account Assignment Group been input in the Customer Master (Billing tabstrips - Accounting sections - Field name: Acct assgmt group).

The Account Assignment Group will be copied automatically into the sales order.

Check whether the configuration in transaction VKOA have been done correctly.

Check whether the sales order (VA03 - Goto - Header - Financial Accounting - Field name: AcctAssgGr) have been filled in automatically.

Check whether the billing document (VF03 - Goto - Header - Header - Field name: AcctAssgGr) have been filled in automatically.

If the customer master have not been maintained and the user have already input the sales order, then the user will have to maintained the Account Assignment Group manually either in the sales order or the billing documents.

Take note for One Time Customer, the user have to input the Account Assignment Group manually into the sales order. One Time Customer can be used by many customer, therefore, the system will not be able to determine the Account Assignment Group manually.

BILLING-2

2007-09-09T10:49:00.000-07:00

Default Start Variant for VF04

There are two types of variant in VF04.

One is the selection variant before clicking the Display Billing List Button.

You can set the start variant via SE93 using the Change mode.

The second variant is the Billing Layout display variant.

This is after clicking the Display Billing List Button.

After creating your layout display variant, you can set it by clicking :-

Settings ->
Display Variant
-> Administration

Select the layout display variant you want and click :-

Edit ->
Define default settings

Sales Order Mass Change

2007-09-08T12:34:00.000-07:00

I am a SAP SD consultant and recently faced with two new terms, mass order change and ALV , I also need to know about the transaction code.

There is transaction MASS which can be used to carry out mass changes in the sales order and other objects.

Mass Maintenance: (Use to change multiple fields in multiple documents at the same time). I have done mass change for customers; and orders should work the same way too.

1) Try t-code [MASS] and select sales orders & execute

2) Choose the table or tables for your selection criteria and also for fields you want to change.

Then execute. (suppose your selection criteria fields are from "sales order header data" table and the field you want to change, is in "item data" table)

3) Put in the sales documents(21000000, 21000001) you want to change and also the items(10) you want to change.

- click on " choose selection fields" button
- From the Pool, move the fields you want to the "select fields" using arrows.

4)From mass maintenace menu, click on "Enter new field values"

-click on "sales order item data" tab and choose the field you want to change.
(for example. I want to change plant for item 10)
-enter the new value (of the plant to be)
-click on "Adopt" and execute

5)In "sales order item data" tab, you see the new value of the plant you entered at the top and the old values of item 10 are below.

-click on "change field values" button. you see all the old values are changed to new values.
-save
Note: it will take some time depending on how many records you have.
Check: Go to [SM37] and see the status of the job you are running and once finished, export the spool file to a spreadsheet.
Before you do mass maintenance, go to the particular table in [se16] and get the results. Then do the mass maintenance and compare the results with this one. If they match, then you are good to go.

Note: If you have any user exits that affect the results, ask them to deactivate the MODCHECKS still you are done with mass maintenance & activate them again.

Is there a way to change the billing date on a ton of sales orders with same old billing date to a same new billing date?

This can be done using the mass transaction:

Transaction: MASS
Object Type: BUS2032
Tables: SD Document: Business item data
Sel Field: Billing Date (MASSSDHE and MASSSDPO)
- Or you can just select by document numbers (May be more efficient)
Execute - List will be provide for changes

Sel Chg Fld: Billing Date
Set new billing date value in the New Values field
Click on lower billing date column
Click on Carry out a Mass Change button
Click on Save button

Suggestion is to test this on a few orders in your development system to get a feel on how this works before applying this to any production data. MASS is a very powerful tool.

I have 100000 sales orders whith an incorrect price and I would like to do a massive condition update with pricing type "B" (Carry out new pricing). Is there a transaction or program for this?

Go to VA05 execute the report. Select all sales orders you want to update the price, Go to the Menu EDIT --> MASS Change ---> New Pricing. System will display all the re-pricing options. Select B. It will re-price all the sales orders.

You can try for one or two order initially check the results and if it is OK, then you can do for others.

Release strategy for Sales order

2007-09-08T12:18:00.000-07:00

Is it possible to have release strategy for sales order?

As such SAP standard does not provide release strategy for sales orders similar to purchase orders. However this requirement of your can be satisfied through authorisation profiles; what I mean to say is that the sale order to be kept incomplete by the person who does not have the required authorisation & the person with proper authorisation will complete
it for further processing. This is only one way of meeting your requirement.

In order to emulate a release strategy similar to purchase orders you can use the status profile in sales documents (BS02).

IMG-Sales and distribution-Sales-Sales documents-Define and assign status profile.

Consignment Sales Process in SAP

2007-09-08T12:10:00.000-07:00

The consignment process in SAP standard consist of four small processes:

Consignment fillup (send materials to customer consignment).
Here you have a consignment fillup order and a consignment fillup delivery.

Consignment issue (issue materials from customer consignment to the customer).
Here you have a consignment issue order, consignment issue delivery and a consignment issue invoice. (the flow is very similar to a normal OR flow, but the materials are issued from the consignment stock instead of plant stock unrestricted).

Consignment return (return materials from customer ownership to customer consignment).
Here you have a consignment return order, consignment return delivery and a consignment return invoice. (the flow is very similar to a normal RE flow, but the materials are returned to the consignment stock instead of plant stock returns).

Consignment pickup (pickup consignment stock and move it to plant stock).
Here you have a consignment pickup order and a consignment pickup delivery.

Note that in consignment fillup and consignment pickup there are no invoices since there is no change of ownership for the materials.

How to perform a consignment order?

In consignment orders you are allowing the stock to sit in your customer location. Once he informs that he used the stock you will invoice him. If he returns the stock you will accept the stock to take it back.

It is defined in 4 steps.

1. Consignment fill up:

Sales document type is KB
Item category KBN
shedule line category E1

In this step, you are not invoicing the customer. document flow is sales order ---- delivery item category. It will not be relevent for billing and pricing because you are not charging money for these goods in this step.

In schedule line category, you will set movement type 631 & set for availability check and TOR.

2. Consignment Issue.

Once the customer informed you that he used all the goods or partial goods then you will create consignment issue for used goods.

Sales document: KE
Item category: KEN
shedule line category: C0 or C1

Here you are invoicing the customer(because he used the goods). you are assigning the delivery documnt and billing document to the sales document.

In item category, you are setting relevent for billing, pricing, special stock.

In schedule line category, your setting is 633 movement type, relevent for availability check & TOR.

3. Consignment Return:

Customer found that some goods are damaged or he not able to sold the goods he want to send it back. that you are creating this document.

Sales document type: KR
Item category: KRN
Shedule line category: D0

You will assign delivery document and billing to sales document. you will create return order, return delivery, return billing.
Your setting item category relevent for billing, returns, pricing, special stock.
Your setting schedule line item category: 634 movement type, NO availability NO TOR.

4. Consignment Pick up:

Even if you create the consignment return the goods are not come to direct to your plant. For that you need to create consignment pick up. here the owner ship is not changing so you do not need to create billing.
Assign retrun delivery to sales document type.

Sales document: KA
Item category: KAN
schedule line category: F0 & F1

Your setting item category relevent for returns. any shedule line category relevent for 632 movement type, MRP, availability check, delivery.

Now you check your plant stock. Stock will increase.