cancel
Showing results for 
Search instead for 
Did you mean: 

issues

Former Member
0 Kudos

plz can anyone send real time issues to my email id clicksantoo@hotmail.com

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

<b>Billing Document not released to accounting / Accounts determination:</b>

To resolve the error, you can analyze account determination in the billing document. Process:

Goto T.Code: VF02 & Enter Invoice number

Next (On the top most strip) goto Environment

Next (Select Environment) go to Account determination

Next (In Account Determination) select Revenue Account Determination (first option)

This will list all the condition types in the Billing document & analyze each condition & check for which G/L accounts is not determined.

<b>

Possible errors:</b>

1. VKOA not maintained for required combination

Solution: Maintain the combination in VKOA.

2. Account Assignment of Customer / material not maintained in Customer / Material Master (If maintained in combination in VKOA).

Solution:

Option 1 (Standard solution):

step 1: Cancel Billing Document --> Reverse PGI --> cancel Delivery --> Cancel Sales Order

step 2: Maintain Customer master / Material Master correctly.

step 3: Recreate sales Order --> Delivery --> PGI --> Invoicing.

Option 2:

Force the Account Assignment Group of Customer / Material through Debug in change mode of Billing document, which will release Billing Document to Accounting.

3. Account Key not maintained in Pricing Procedure:

Impact: This may create accounting document, but if condition type, which are to be posted to account, but do not have account key maintained in pricing procedure, it will not be post the relevant condition type to G/L account.

4. Billing Document not being released to accounting --

In Material Master, there is some link between Profit Centre & MRP Type. If one of it is not maintained, erratically few documents get stuck while releasing Billing Document to accounting. Few of course get posted.

Solution1: Cancel Billing Document --> Reverse PGI --> Cancel Delivery --> Block the sales Order & Create new sales Cycle all over again after rectifying Material master.

Solution 2: (Temporary Solution) In Debug mode in Billing, force the Profit Center in Billing Document with the help of Abaper. But ensure Material master is rectified.

From FI Side, you require to check that all the G/L account has been maintained through T.Code: FS00. G/L account being Master data has to be created in each client to upload through LSMW / SCATT / BDC.

In Billing Document in change mode (in the first screen where we enter Billing Document number), on the top most left hand corner, take a dropdown on Billing Document & select Release to accounting. Here you can get the under mentioned possible message:

1. G/L account not found

2. Cost Element not maintained for G/L account.

In both the above cases, FI consultant requires to take corrective action.

<b>Pricing:</b>

This is very specific & differs from client to client & may also differ based on scenario.

Write-up on Pricing -

In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.

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.

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.

It is assumed that document pricing procedure, customer pricing procedure , ... are in place.

Sales Document not assigned to Sales Area:

SPRO --> Sales & Distribution --> Sales --> Sales Documents --> Sales Document Header --> Assign Sales Area To Sales Document Types --> Assign sales order types permitted for sales areas (do ensure to maintain combined Sales organization, combined Distribution channel & combined division. for eg: Sales org 1000 & sales org 1000, Sales org 2000 & sales org 2000, & so on ....

similarly for distribution channel & Division, so that the Sales area combination is available for assignment to Sales Document Type.)

Issues related to Customer Master data:

1. what is the impact of leaving customer pricing procedure & customer statistic group blank in customer master --> sales area data --> sales tab:

If Customer Pricing Procedure is left blank, Pricing will not be determined.

If customer statistic group is left blank, then data will not flow to standard reports.

2. Who maintains reconciliation account in customer master?

Ideally, reconciliation account is maintained by FI person, but if SD person is authorized & has the knowledge of which reconciliation account to be maintained, then even SD person can maintain the same.

3. Terms of payment appear in Company Code Data & sales Area Data. What is the impact of each? why is it not populated automatically, once it is maintained at either field?

Terms of payment from company code data is for reporting purpose & it is from sales area data that it flows to sales order.

It is a standard feature of SAP that it is not populated automatically if maintained at either of the field, but it is a must in sales area data & can be skipped in company code data.

4. Unable to select Sales Area for Customer Master Creation?

Most Probably either sales area is not defined or customization not done for common Sales Org & Common Distribution Channel. To maintain this configuration: SPRO --> Sales & Distribution --> Master Data --> Define Common Distribution Channels / Define Common Divisions

Other queries:

Where is the control for Automatic PGI?

For this you can set batch jobs. T-code SM36, 37 38 or you can use the userexit CSO_P_DLVRT_GOODS_ISSUE_CREATE - auto PGI

The above are few examples.

/message/3690162#3690162 [original link is broken]

Message was edited by:

sam masker

Answers (4)

Answers (4)

Former Member
0 Kudos

Hi Santosh,

1. When we go through VA02, Payments term field should be display. So user not able to change any value?

ans. Using Screen exit u can solve it.

2. when we go through VA01, order type field as Required?

ans. using transaction variant(SHD0) you can solve it.

3. Creating new order reason?

ans. SPRO > SD > Sales> Sales doc. > Sales doc. header > define order reason

4. Adding a default sold to party in the sales order creation?

ans. Using field exit EXIT_SAPMV45A_002. You can solve it.

Reward points if it helpful

Cheers,

Govind.

former_member227476
Active Contributor
0 Kudos

dear santhosh

1. What is an EDI invoice, how it reflects in SAP R3 system?

Quite generally, you create an invoice by a normal way, but after this you generate an output (print document) in the form of an IDOC. This IDOC can be sent to the customer. The process is similar to the standard print output of the invoice. The IDOC should be of a message type INVOIC. The function module is IDOC_OUTPUT_INVOIC.

There is also a self-billing process with the invoice creation. In this case the customer sends the IDOC for himself. This IDOC must be processed via EDI on SD side, and then the SD invoice will be created. To learn this process, please call the function module IDOC_INPUT_SBINV in the transaction SE37 and the press the button "Function Module Documentation". The SBINV process can be realized via EDI only.

2. What is meant by Explosion in SD?

It is related to Bill Of Material where one parent item is linked with several child items. For creation/edit/display, T-Code is CS01/02/03

3. What is the usage of configuration profile in variant configuration?

You maintain the configuration parameters for a configurable general maintenance task list in the configuration profile.

The settings that you make here also concern the BOM explosion for the piece of material. In addition, at least one class, whose class type allows variant configuration, must be assigned to each configuration profile. The class contains the characteristics that the system proposes for characteristic evaluation when you create a maintenance or service order.

4. What do you mean by tickets? Could you please give me some examples of tickets?

Tickets in SD can be considered as the problems which the end user or the employees in the company face while working on R/3. Tickets usually occur during the implementation or after the implementation of the project.

There can be numerous problem which can occur in the production support and a person who is working in the support has to resolve those tickets in the limited duration, every ticket has the particular deadline alert so your responsibility is to finish it before that deadline.

End user is not able to

1. Create Sales order for a customer from a new plant, since shipping point determination is not happened. (Without shipping point the document becomes INCOMPLETE and he will not be able to proceed further like DELIVERY, BILLING).

He raises a ticket and the priority is set in one of the below

1.Low 2. Medium 3. High.

Now you need to solve this ticket. You would analyze the problem and identify that the SP configuration has to be done for the new plant.

You would request a transport for DEV CLIENT to BASIS. You do the change and Request one more Transport to BASIS for QA client. The End user will test the same by creating a sales order for the new plant and approve it.

Finally u request a transport to move the changes to PRODUCTION.

Once the change is deployed in production the TICKET is closed.

What I have given is a small ex. You would get some real issues with severity HIGH in your day-day support

1. KOFO error?

2. Defecit in sales order stock?

3. PGI is not possible?

4. Shipping conformation is not possible.

5. Picking or packing PGI is not possible.

5. What is the difference between sales process and business process?

BUSINESS PROCESS: Sequentially and logically related series of processes and functions for an internal or external target group to deliver a defined good or service. The R/3 Reference Model provides sample business processes in scenarios as EPCs.

6. What is the difference between transit time and transportation time?

Transit time: is the time taken by the material to reach customers place.

Transportation time: is the time taken to schedule the materials by shipping company.

7. What is the difference between free goods and bonus buy?

Free goods are either inclusive or exclusive if a customer orders for 10 products he will get 1 free for that no price is charged this is exclusive scenario

If a customer orders 10 products he will get 9+1 for 1 product he will not charged this inclusive scenario

For bonus buy if a customer orders regularly 10 products in one occasion if he orders 1000 products he will be given less price than the price he will get for 10 products this bonus buy scenario

Or

Free goods are considered to be merchandise, moveable belongings or personal property. Free goods are those which economists are not interested in because in free goods doe not offer the opportunity for creating a cost for usage. The best example of free goods is air because there is no scarcity of air. Economists are interested only in goods, which can be manipulated to create cost for usage. Free goods are plentiful; you have as much as you want without a chance for future cost to society.

A bonus buy refers to any product manufactured or otherwise made available for purchase at a lower cost for a certain period of time. A bonus buy can relate to food, cars, stocks, bonds, insurance, bank loans or almost any product you can think of.

Examples of Bonus buys are: buy one and get one free, 20% original price, 15% Reduced Mortgage today.

8. What is the difference between static and dynamic in credit management?

SIMPLE CREDIT CHECK: Tr.Code - FD32

It Considers the Doc.Value + Open Items.

Doc.Value: Sales Order has been saved but not delivered

Open Item: Sales Order has been saved, Delivered, Billed & Transferred to FI, but not received the payment from the customer.

Eg: Customer Credit Limit is Rs.1, 00,000/-

Suppose Doc.Value + Open Item Value is Rs.1, 10,000/-

Here credit limit exceeds then system reacts.

Options: A) Warning Message

B) Error Message (Sales Order won't be saved)

C) Error Message with Delivery Block

AUTOMATIC CREDIT CHECK: Give extra credit facilities to the particular customer.

STATIC CREDIT LIMIT DETERMINATION: Checking Group + Risk Category + Credit Control Area.

A) Credit Checking Groups: Types of Checking Groups.

01) Sales

02) Deliveries

03) Goods Issue

At all the above 3 levels orders can be blocked.

B) Risk Category: Based on the risk Categories Company will decide how much credit has to give to the customer.

HIGH RISK (0001) : LOW CREDIT

LOW RISK (0002) : MORE CREDIT

MEDIUM RISK(0003) : Average Credit

Static Credit Check it checks all these doc value & check with the credit limit

1) Open Doc.Value / Sales Order Value : Which is save but not delivered

2) Open Delivery Doc.Value : Which is delivered but not billed

3) Open Billing Doc.Value : Which is billed but not posted to FI

4) Open Item : Which is transferred to FI but not received from the customer.

DYNAMIC CREDIT CHECK : 1) Open Doc

2) Open Delivery

3) Open Billing

4) Open Items

5) Horizon Period = Eg.3Months

Here the System will not consider the above 1,2,3& 4 values for the lost 3 months

Then assign the Sales Doc & Del Documents.

Sales Doc.Type (OR) + credit Check (0) + Credit Group (01)

Credit Limit Check for Delivery Type: Del.Type (LF) + Del Credit

Group (02) + Goods Issue Credit Group (03)

rewards if it helps

siva

2. Account Assignment of Customer / material not maintained in Customer / Material Master (If maintained in combination in VKOA).

Solution:

Option 1 (Standard solution):

step 1: Cancel Billing Document --> Reverse PGI --> cancel Delivery --> Cancel Sales Order

step 2: Maintain Customer master / Material Master correctly.

step 3: Recreate sales Order --> Delivery --> PGI --> Invoicing.

Option 2:

Force the Account Assignment Group of Customer / Material through Debug in change mode of Billing document, which will release Billing Document to Accounting.

3. Account Key not maintained in Pricing Procedure:

Impact: This may create accounting document, but if condition type, which are to be posted to account, but do not have account key maintained in pricing procedure, it will not be post the relevant condition type to G/L account.

4. Billing Document not being released to accounting --

In Material Master, there is some link between Profit Centre & MRP Type. If one of it is not maintained, erratically few documents get stuck while releasing Billing Document to accounting. Few of course get posted.

Solution1: Cancel Billing Document --> Reverse PGI --> Cancel Delivery --> Block the sales Order & Create new sales Cycle all over again after rectifying Material master.

Solution 2: (Temporary Solution) In Debug mode in Billing, force the Profit Center in Billing Document with the help of Abaper. But ensure Material master is rectified.

From FI Side, you require to check that all the G/L account has been maintained through T.Code: FS00. G/L account being Master data has to be created in each client to upload through LSMW / SCATT / BDC.

In Billing Document in change mode (in the first screen where we enter Billing Document number), on the top most left hand corner, take a dropdown on Billing Document & select Release to accounting. Here you can get the under mentioned possible message:

1. G/L account not found

2. Cost Element not maintained for G/L account.

In both the above cases, FI consultant requires to take corrective action.

Pricing:

This is very specific & differs from client to client & may also differ based on scenario.

Write-up on Pricing -

In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.

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.

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.

It is assumed that document pricing procedure, customer pricing procedure , ... are in place.

Sales Document not assigned to Sales Area:

SPRO --> Sales & Distribution --> Sales --> Sales Documents --> Sales Document Header --> Assign Sales Area To Sales Document Types --> Assign sales order types permitted for sales areas (do ensure to maintain combined Sales organization, combined Distribution channel & combined division. for eg: Sales org 1000 & sales org 1000, Sales org 2000 & sales org 2000, & so on ....

similarly for distribution channel & Division, so that the Sales area combination is available for assignment to Sales Document Type.)

Issues related to Customer Master data:

1. what is the impact of leaving customer pricing procedure & customer statistic group blank in customer master --> sales area data --> sales tab:

If Customer Pricing Procedure is left blank, Pricing will not be determined.

If customer statistic group is left blank, then data will not flow to standard reports.

2. Who maintains reconciliation account in customer master?

Ideally, reconciliation account is maintained by FI person, but if SD person is authorized & has the knowledge of which reconciliation account to be maintained, then even SD person can maintain the same.

3. Terms of payment appear in Company Code Data & sales Area Data. What is the impact of each? why is it not populated automatically, once it is maintained at either field?

Terms of payment from company code data is for reporting purpose & it is from sales area data that it flows to sales order.

It is a standard feature of SAP that it is not populated automatically if maintained at either of the field, but it is a must in sales area data & can be skipped in company code data.

4. Unable to select Sales Area for Customer Master Creation?

Most Probably either sales area is not defined or customization not done for common Sales Org & Common Distribution Channel. To maintain this configuration: SPRO --> Sales & Distribution --> Master Data --> Define Common Distribution Channels / Define Common Divisions

The above are few examples.

/message/3690162#3690162 [original link is broken]

Former Member
0 Kudos

Hi,

Many of the issues which are getting posted in this forums are real time issues. I suggest you to visit this forum regularly to see the questions form the consultants who are facing issues, and the replys.

Prase

Former Member
0 Kudos

Hi Santhosh,

Please find the below some important issues :

1. What is EDI invoices, how it reflects in SAP R3 system

Ans: Quite generally, you create an invoice by a normal way, but after this you generate an output (print document) in the form of an IDOC. This IDOC can be sent to the customer. The process is similar to the standard print output of the invoice. The Idoc should be of a message type INVOIC. The function module is IDOC_OUTPUT_INVOIC.

There is also a self-billing process with the invoice creation. In this case the customer sends the IDOC for himself. This IDOC must be processed via EDI on Sd side, then the SD invoice will be created. To learn this process, please call the function module IDOC_INPUT_SBINV in the transaction SE37 and the press the button "Function Module Documentation". The SBINV process can be realized via EDI only.

2. What is meant by Explosion in SD?

Ans: It is related to Bill of Material where one parent item is linked with several child items. For creation/edit/display, T-Code is CS01/02/03

. What is the usage of configuration nprofile in variant configuration

Ans: configuaration profile is a place where we will configure configurable material (mmk1) with class type 300 and class which u have defined. Here the values of variant characteristics will be stored

or

a). We use the configuration profile to assign the configurable material to one or more variant classes. This links the material to the characteristics of the class for configuration.

b).You can define settings that affect the display options and scope of characteristics on the

value assignment screen. (i.e. CU50)

c). You can use the configuration profile to assign dependencies to a configurable object.

d). For maintaining configuration parameters for BOM explosion.

You maintain the configuration parameters for a configurable general maintenance task list in the configuration profile.

The settings that you make here also concern the BOM explosion for the piece of material. In addition, at least one class, whose class type allows variant configuration, must be assigned to each configuration profile. The class contains the characteristics that the system proposes for characteristic evaluation when you create a maintenance or service order.

4. What do you mean by tickets? Could you please give me some examples of tickets?

Ans: Tickets in SD can be considered as the problems which the end user or the employee in the company face while working on R/3. Tickets usually occur during the implementation or after the implementation of the project.

There can be numerous problem which can occur in the production support and a person who is working in the support has to resolve those tickets in the limited duration, every ticket has the particular deadline alert so your responsibility is to finish it before that deadline.

End user is not able to

1. Create Sales order for a customer from a New plant, since shipping point determination is not happened. (Without Shipping point the document becomes INCOMPLETE and he will not be able to proceed further like DELIVERY, BILLING).

He raises a ticket and the priority is set in one of the below

1.Low 2. Medium 3. High.

Now you need to solve this ticket. You would analyze the problem and identify that the SP configuration has to be done for the new plant.

You would request a transport for DEV CLIENT to BASIS. You do the change and Request one more Transport to BASIS for QA client. The End user will test the same by creating a sales order for the new plant and approve it.

Finally u request a transport to move the changes to PRODUCTION.

Once the change is deployed in production the TICKET is closed.

What I have given is a small ex. You would get some real issues with severity HIGH in your day-day support

1. kofo error?

2. Defecit in sales order stock?

3. Pgi is not possible?

4. Ship conformation is not possible?

5. Picking or packing pgi is not possible?

5. What is the difference between sales process and business process?

Ans. Sales Process: is also a business process where in only sales related activities are involved. I.e. for e.g.: sales order, purchase order, etc.,

Business Process: any activity or business event where in business is involved we can those processes as Business Process

BUSINESS PROCESS: Sequentially and logically related series of processes and functions for an internal or external target group to deliver a defined good or service. The R/3 Reference Model provides sample business processes in scenarios as EPCs.

6. What is the difference between transit time and transportation time

Ans:

Transit time: time taken by the material to reach customers place. for eg: this is the time period right after the goods have left the shipping point of the business to the customer till the goods are received by the customer at his place..

Transportation time: time taken to schedule the materials by shipping company. For eg: this is the time period right from the material manufacturing to the delivery of the material to the customer.

Transit time: is the time taken by the material to reach customers place.

Transportation time: is the time taken to schedule the materials by shipping company.

7. What is the difference between free goods and bonus buy?

Ans. Free goods are either inclusive or exclusive if a customer orders for 10 products he will get 1 free for that no price is charged this is exclusive scenario

If a customer orders 10 products he will get 9+1 for 1 product he will not charged this inclusive scenario

For bonus buy if a customer orders regularly 10 products in one occasion if he orders 1000 products he will be given less price than the price he will get for 10 products this bonus buy scenario

Or

Free goods are considered to be merchandise, moveable belongings or personal property. Free goods are those which economists are not interested in because in free goods doe not offer the opportunity for creating a cost for usage. The best example of free goods is air because there is no scarcity of air. Economists are interested only in goods, which can be manipulated to create cost for usage. Free goods are plentiful; you have as much as you want without a chance for future cost to society.

A bonus buy refers to any product manufactured or otherwise made available for purchase at a lower cost for a certain period of time. A bonus buy can relate to food, cars, stocks, bonds, insurance, bank loans or almost any product you can think of.

Examples of Bonus buys are: buy one and get one free, 20% original price, 15% Reduced Mortgage today.

8. Difference between 4.6 version and 4.6c ,4.7ee

Ans. There are so many differences between the versions in different objects

1. In the customer master in 4.6 version there is no partner function tab in the customer in xd01 t-code and also there is no CIN tab in that version but it is there in the 4.7 EE version

This is the major change from the 4.6cc to 4.7EE

2. in 4.7EE there is some settings that are related for CIN which cannot be done in 4.7EE that means they need some patches for doing the configuration setting for the CIN

But we can do the same in the 6.0 versions

These are the some of the settings that are differed in the two versions and in that two objects

9. can you able to delete the company code data in customer master data?

Ans: No you cannot delete company code..

10. what is the tool used in sap sd support to communicate with the user for handling the tickets

Ans: CITRIX is the tool to acces client's enviornment.Under CITRIX u can find an icon called SYNERGY (in synergy u can check your tickets.)

11. What is the main difference of revenue key for e.g.:- ERL and accrual key e.g.:- ERU

A. ERL – Sales Revenues and ERU - Accrual.

12. What makes delivery create if the cash sales order type is order related billing?

A. IN VOV8 IN SHIIPING IMMEDIATE DELIVERY AS "X"

Hope this will definelety Helpful to you and Please Reward If Really Helpful,

Thanks and Regards,

Sateesh.Kandula