support Issues Reg.

[Former Member]

Hi SAP Gurus,

When u r in support project,the problems end users r facing gets esclated to u and u resolve these issues logging on to the dev server etc and make changes.

(please correct me if i am wrong in the process) which go to qas and subsequently to pro server.

My question is :

- when customizations is done all this things are taken care off,why again change the settings ?

- Are all the support issues related to changes to be made in the basic settings.

- Till what point we can change the basic settings.and authorisation given for the same.

If some one could send me some realtime support issues to my email id

anandsutram@yahoo.co.in.

is highly appreciated and rewarded.

Thanx in Advance

Narender.N

[former_member227476]

dear narender,

i hope rajesh has given nice solution

always i suggest all the friends who are posting for the tickets, these are nothing but issues which were sent by the users.

the best way is you pls note what all the problems you are facing while practicing.

you know the better why how to give the answer for that issue when the interviewer ask you.

this is my sincere advice

one more thing is here in this group, we are all posting so many issues which are real time what we have recived so far.

support is basically do give the clint for his errors and for new developments new requirements and new business changes its all depends on these

do practice and all the best..

siva

[Former Member]

This message was moderated.

[Former Member]

HI Narender,

Sent Mail.

Reward Points if it helps.

Narender, when you are in support project you are actually working most of the time in production server and not in dev server. Only if any change needs to be done in config / layout / form etc then you will go to Dev serever make changes and move it to QA and Production server. My mail has some real time tickets they will be helpful

Regards

Srini

[Former Member]

Hi

Sent the mail Reward if helps

[Former Member]

Dear Narendra,

During Implementation, proper care is taken, so that the issues are plugged. But still changes are bound to come due to:

1. As per change in requirement.

2. Improper User Testing during Implementation.

3. New Requirement.

4. New Developments.

5. Issue related to Master data error which acts as a block in process.

& several other reason.

Some Real Time Tickets:

Real Time Issue:

Billing Document not released to accounting / Accounts determination:

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.

Possible errors:

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.

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]

Regards,

Rajesh Banka

Reward suitable points.

• How to give points: Mark your thread as a question while creating it. In the answers you get, you can assign the points by clicking on the stars to the left. You also get a point yourself for rewarding (one per thread).

[Former Member]

hi,

Email sent to mail id

REward points if the answer is helpful

Regards,

Murali