SAP Real Time Content

SYSTEM LANDSCAPE:-

1. What is System Landscape?

System Landscape is a key design decisions for distributing the SAP
applications across the servers.

The System Landscape is design by BASIS Team.

DEVELOPMENT QUALITY PRODUCTION

100- Golden Client. 100-Testing Client. 100- Pre Production.

110- Golden Test Client. (Integration Testing) 110-Production Client.
120-Sand Box. 110-Training Client.

I. Development Server – Development System – Development Environment:-

1. Client 100- Golden Client- Development Client – Configuration Client: It is a Client

where the functional team do configuration as per client requirement and ABAP team
develop the Programs, Reports etc.

We Should not Create any Master data and post transaction data in this Client.

2. Client 110- Golden test Client – Development Test Client- Configuration Test
Client:

This is a Client where we do most of unit testing by functional team and development
teams.

Note: Where do you Perform Unit Testing?

Ans : Development Test Client.

This Client is not modifiable.

3. Client 120 – Sand Box: This is a Client used by Configurators and developers to do
research and prototyping of how to fulfill of project requirements and to do experiments
to their Skills.

In Sandbox system doesn’t generate transport request.

II . Quality System – Quality Server – Quality Environment.

1. Client 100- Testing Client: This is a Client where we do perform Integration Testing by
Functional Teams.

This Client is also not Modifiable.

1
SAP Real Time Content

Where do you Perform Integration Testing?

ANS: In Quality System.

2. Client 110 – Training Client: This is a Client where we prepare end user Manuals and
Conduct training for end users.
In which phase conduct end users training?
ANS: Final Preparation Phase.

III. PRODUCTION SYSTEM:

1. Client 100 – Pre production Client: It is nothing but mirror of production client
where we can simulate.

This client can be used to upload transactional data in to SAP before production
system. This client helps us to simulate the similar kind of issues in production
systems.

This client is also not modifiable.

2. Client 110- Production Client: This is the client where the end users post day to day
live transactions.

This client is also not modifiable.

2
SAP Real Time Content

TRANSPORT REQUEST MANAGEMENT

Transport Request is like a vehicle which is used to carry out the changes from
one client to another client.

How Many types of Transport Requests:

1. Customizing request.
2. Work Bench request.

1. Customizing Request : Generally customizing request will be generated for all

customizing activities . ex: Company code creation, Set up APP etc.,

This is Client Dependent.

2. Work Bench Request: Generally Work Bench request will be generated for objects,
Programs developing, Maintain Validation rules, Create Variants.

This is Client Independent.

# Dependent Means It is Available across all clients all the servers.

How many types of request status available in SAP?

1. Modifiable.

2. Released.

1. Modifiable: The Request not at released and reusable.

2. Released: The Transport Request was released.

NOTE: Once Transport request was released it can not be reusable.

How to release transport request (TC: SM09 / SM10):

➢ User: SAPUSER.
➢ Select Customizing request check box.
➢ Select Modifiable check box & deselect released check box.
➢ Select display button.
➢ Expand the transport request number.
➢ Keep the cursor on customizing task number.
➢ Click on release directly button (F9). (Truck symbol).
➢ Keep the cursor on Main request number.
➢ Click on release directly button.
3
SAP Real Time Content

➢ Click on refresh button.

➢ Select back arrow button.
➢ Deselect Modifiable check box & Select released check box.
➢ Select display button.
How to Import the changes from one client to another client:
Ex: Development: 100 to Development: 110 in same server.
➢ Go and Login to Target client.
➢ Go to TC: SCC1.
➢ Source Client : 100
➢ Transport Request: DM0K900055 (Note down request no & Enter here).
➢ Select Including Request Sub Task.
➢ De select test run check box.
➢ Select Start Immediately button.
➢ Click on Refresh button.
➢ Go and Check Changes.
How to Import the changes from one Client to another Client from different
Servers:
➢ Go and Login to the Target Client. (Ex: Development 100 to Quality 100).
➢ Go to TC : STMS (STMS : SAP Transport Management System)
➢ Click on Import overview button & Press enter.
➢ Double click on Transport request number.
➢ Specify the source client (Ex: Development 100).
➢ Click on refresh button.
➢ Go and check the changes.

4
SAP Real Time Content

TYPES OF PROJECTS:

1. Implementation project / Development Project.

2. Support & Maintenance Project.
3. Up gradation Project / Migration Project.
4. Roll out Project.

1. Implementation Project: It is a Pure development kind of project where we map /

design client business requirements in SAP system for the first time by using ASAP
methodology.

2. Supporting & Maintenance Project : After implementing SAP successfully for

the Client we would provide support and Maintenance to the client in daily day to
day business transactions.

Roles & Responsibilities:

✓ Issues Resolution.
✓ Provide assistance to the users during month end and year end activities.
✓ Configure the new activities to the existing system as on when required.
3. Up gradation / Migration Project :Migrating from old version to new version
Ex: From 4.7 EE to 6.0.
4. Roll out Project: Implementing` SAP for another country / Plant / Legal entity
based on existing country / existing one. They were already in to SAP for long back.

5
SAP Real Time Content

ASAP METHODOLOGY: (Accelerated SAP Methodology)

It is a method / Process which we used to implement SAP to our Clients

Successfully.

It Contains road map of 5 Phases.

1. Project Preparation Phase.

2. Business Blue print Phase.
3. Realization Phase.
4. Final Preparation Phase.
5. Go Live & Support Phase.

1. Project Preparation Phase :

✓ Servers set up.

✓ Resource Recruitment.
✓ Conducting SAP awareness training to core team members.
✓ Prepare the project charter.
✓ Project planned.
✓ Gathering ASIS documents from client.
✓ Kick off.
2. Business Blue Print Phase :
✓ Conducting work shops (By Consultants)
✓ Preparation of GAP analysis documents.
✓ Preparation of Configuration documents.
✓ Writing functional specification.
✓ Preparation of all Deliverable documents like BPML, BPP, BDD.
3. Realization Phase :
✓ Configure the system as per configuration document.
✓ PRICEFW objects developing by technical team.
✓ Provide test data for development objects.
✓ Preparation of end user Manuals.
✓ Resolved defects raised during testing.
✓ Involved in Unit testing and Integration testing.
4. Final Preparation Phase :
✓ Conduct end user training.
✓ Involved in cut over Simulation Plan.

6
SAP Real Time Content

✓ Involved in Cut over activities.

5. Go Live and Support phase :
✓ Move Transport request in to production system.
✓ Provide continuous Support.
✓ Involved post implementation support activities.

7
SAP Real Time Content

TICKET MANAGEMENT:
1. What is Ticket?
It can be an incident, a defect, a problem, a issue.
2. What is the Tool you have worked on in your supporting project?
a. Service Manager
b. HP Service Desk (HPSD)
c. Remedy.
3. What is the Tool you have used for defects management in your implementation project?
HP Quality Centre (HPQC).
4. How Many levels of Support you have provided to your Client?
a. Level 1
b. Level 2
c. Level 3
d. Level 4
e. Level 5
a. Level 1: Interaction Tickets, Request Types.
b. Level 2: Problems, Transactional data
# Level 1 & Level 2 is provided by Help desk.
c. Level 3: Issues resolution, code fixing by ABAP team.
d. Level 4: New Changes to the existing system, develop new programs through
change request.

5. What is SLA?

It is a service level Agreement. It is an Agreement between service Provider &

Customer.

6. How many types of status one Ticket can have?

a. Open / New.
b. Assigned.
c. Work in progress.
d. Waiting for Inputs / Pending with Customer / Pending with Vendor (SAP).
e. Waiting for closure confirmation.
f. Close.
7. What is your severity?
a. I – With in 8 hrs.
b. II – 3 Working days.
8
SAP Real Time Content

c. III – 1 Week.
d. IV – 1 Month.

SOME OF REAL TIME ISSUES:

1. I need your help in credit Management, some customer Credit limit is not shown in VKM4
transaction, for example for customer 6113784 limit is not shows. anyone help me what is
the problem behind this ?
# Credit limit in FD32,

2. Hello all,

• The client is using Multi Cash format for Electronic Bank statement.
• They want the 'Reference' field(BKPF-XBLNR) of Payment document to be updated with
UTR (Unique Transaction reference) number provided by the bank in the bank statement
in one of the Note to Payee fields, when Bank statement is uploaded through T.Code: FF.5
.
• The UTR is to be updated only for e-payments(NEFT / RTGS).
Earlier, when the client was using MT940 format, the UTR was updated separately by
way of a customized program; but now they do not want to use any customized program for
the UTR updation; it should happen at the time of uploading the Multi cash statement.
Would like to know whether field can be updated when bank statement is uploaded; if yes,
please let me know the procedure.

3. I am facing an issue in customer underpayments with T-code F-28 in ECC6.

For underpayments the system is only considering the percentage figure in the tab "Cash
Discount per line item" in OBA4 setting.

The expectation is that the system should consider the minimum of the "amount" and
"percent" figures given in the tab "Permitted payment differences".

If anyone has come across such an issue and /or knows the solution, please get back to me
with the same

4. I am facing issue with Asset Retirement data upload through LSMW. using IDOC BAPI
method.

While uploading Asset Master and Acquisition it get successfully uploaded now When I
am trying to upload Asset Master and Retirement data I am getting error saying "Could not
find transactions in table for the values in table PROPORTIONALVALUES"

5. We have a requirement in our Australian Project to create a File format for BPay-
Citibank Australia to be used when running the Automatic Payment program(F110).

9
SAP Real Time Content

Hi All,

We are implementing functionality of automatic email communication of Payment advice.

We need to implement this for payment method which is classified as Bank transfer.
Currently classic payment medium is set for relevant payment method in country. Program
assigned in classic payment medium is RFFOM100. While doing payment run users assign
variant to this program.

With all the settings specified below we could successfully send mail to email id
maintained in vendor master record. But after these changes we are not able to send file to
bank (which happens through z transaction which is run after payment run).

Can anyone suggest how we can achieve objective of sending payment advice through
email to vendors without disturbing current functionality of bank transfers.

Following are the steps which we have implemented so far.

1. Creation of functional module

2. Assign functional module to BTE

10
SAP Real Time Content

3. Activated Payment medium workbench for Payment method in country.

11
SAP Real Time Content

4. Assigned form for paying company code.

12
SAP Real Time Content

5. Payment advice control settings in payment method for company code.

13
SAP Real Time Content

Ticket Management:
To start with, we receive a incident ticket.
Initially on receipt of a ticket, it is in an accepted phase. Usually when a ticket is
received from the ASD and it is assigned to the consultant it is in the accepted phase.
For tickets that have been received from other teams the phase might be different
which we shall deal with later.
Step1: Incident status change
Initially when a ticket is assigned it would appear as given below:

This status needs to be changed to “Work in progress”.

Step2: Change the Incident title appropriately.
The incident title needs to be meaningful, if by change it is not meaningful ,
please correct the same appropriately.
The incident title is also used for tracking and other monitoring purposes. To
accommodate the same, a set codification has been put in place which should be
prefixed to the incident title.
One such codification can be explained here. For a complete list of codification,
kindly refer the excel file attached.

WI|WF|1|30/09
WI – Stands or Work in progress
| - We can get this by clicking shift and “\” button.
WF – Stands for Workflow
1- Stands for ticket category
30/09 – Expected date of closure.

The incident title after incorporating the codification would for example look as

The excel file with the relevant codes is attached herewith for your reference.

Ticket CodesV3 0
(3).xls

Step 3: Check the Asset:

The asset will usually be correct, if it is coming from the ASD. However, if it is
being reassigned by a different team, or if it is a secondary ticket, then the asset might
be with a different name. All tickets should be related to P94 system. The following is
standard notation of the asset.

14
SAP Real Time Content

ERP-SAP_GSAPOP_P94_FI-(Relevant subcategory, for example AR, AP, CO etc.).

So a correct asset, for example would look like this:

In case the asset shows any other asset, then it needs to be corrected. To do the
same, delete the asset appearing in the field and input “ERP-SAP_GSAPOP_P94_FI”
and click on search tab i.e. . The system populates the relevant assets with
subcategories, choose the correct one and proceed.

In the process of changing the asset, the system might prompt for entering a
subcategory. The subcategory should always be GSAP-OP. Similarly the category is
always DOWNSTREAM.

Step 4 : Verify the proble

m type.

The problem type in the incident ticket, signifies the type of problem. On a
broad level, we can categorize the tickets as, Request type tickets and Non-request type
tickets. The request type tickets are those tickets, that would involve a change in the
system. This could be either a configuration change or a ABAP code change.

An example of a Request type ticket would be “ To add GL account to a Set”,

“Create a storage location”. Etc.

In such cases, the word “Request” needs to be added to the incident title. An
example is as shown below.

So whenever we have a ticket that needs a change or during the course of

investigation it leads to a change then the problem type needs to changed to Request
and the incident title changed accordingly.

The other category i.e. Non request type could be

15
SAP Real Time Content

The problem type needs to be selected appropriately. The problem type is an

important component, because there are other dependent activities/ score cards that are
dependent on this.
Once when a change is done in an incident ticket, the system expects to update
the type of activity and the amount of time spent, without which it would not save the
changes. Choose the appropriate activity type i.e. and input the appropriate time spent
and save the change.

Step 5 (a) : Acknowledgment mail for Severity 3 and 4 tickets .

Once a ticket is assigned, the owner of the ticket needs to be intimated that the
ticket has been assigned and you are working on the same.

The owner’s short id is given in the incident details tab, in the field contact id

The mail is to be sent to the person’s id that is mentioned in the contact id field.

The subject line of the mail should contain the details of the Interaction ticket and the
Incident ticket and the severity of the ticket.

Any issue is first reported to the ASD (Application support desk) through an
Interaction ticket. The ASD then looks into the issue and tries to resolve the same. If it
is resolved, the interaction ticket is closed. In case it is not resolved and would require
further investigation, it is escalated to the second level support i.e. us for further
processing. The interaction ticket usually starts with “GSC”, whereas the incident
ticket start with “GIM”. The severity can be seen in the Incident details tab itself.

Kindly keep the team lead in the CC, so that in your absence he would be knowing the
progress and would be able to answer any queries raised.

A standard signature that is to be followed. Kindly do not deviate.

XXXXX (Person’s name)

Downstream IT BAM GSAP Support – FSS
16
SAP Real Time Content

Location : India, Bangalore

Tel : +91 80 226XXXX
e-mail: XXXXX@shell.com

A Template of the acknowledgement mail is attached herewith.

Step 5(b) – Intimation mail for Severity 1 and Severity 2 tickets.

In case of Sev1 and Sev2 tickets, the following template needs to be used, the colored
portion.

Hello Mr. XXXXXXXX ,

I have been assigned to work on the ticket GIM30XXXXX raised by you.

Please contact me for all matters related to this ticket going forward.

Will analyse the issue ASAP and contact you for clarification if required.

For SEV 1 & 2:

Please note that the above ticket is raised as SEV 1 / 2, we may require more
information for analysis and to provide the resolution. Please be available till
resolution provided

If Sl.No.2(Business Impact) is not available in the ticket please include the below
sentence

Further Business Impact not provided in the ticket, please provide same and
revert at the earliest

1.OU Impacted:
2.Business Impact:
3.Status: Brief update the current status:
4.Expected time of Restoration:
5.Possible workaround:
6.Next Update:

(Signature)

17
SAP Real Time Content

I case of Sev1 ticket, the SLA is 4 hours i.e. it needs to be resolved within 4
hours, similarly for Sev2 ticket, the SLA is for 8 hours i.e. it needs to be resolved in 8
hours.

In case of Sev1 and Sev2 tickets the following people need to be kept in CC
mandatorily.

i) Team lead and Delivery Manager

ii) Focal Point
iii) GX DS IT BAM ERP GSAP AS – FSS (Application specialist group).

Step 6: Closure Confirmation Mail.

In case the issue is resolved/ the resolution is known, follow the instructions below,
else see step 9 onwards.

A closure confirmation mail needs to be sent to the user/business. The format

for the same is attached herewith.

The subject line should clearly state that it is a closure confirmation mail.

Step 7 : Ticket closure process.

On receipt of confirmation from the user to close the ticket the following process needs
to be followed:

a) Change the status of the ticket to “Work in progress”

b) Recheck the problem type and asset.
c) Fill in the PA (Problem analysis) template for all non request type tickets and
attach it to the Incident ticket. A sample PA template is given herewith.

GIM30177683 PA.xls

d) The closure template needs to be filled in the closing comments. The template
to be followed would be as follows:

Issue:
Analysis:
Resolution:

User Confirmation: (The mail received from the user needs to be forwarded and then
copied and pasted so that the date and other details also get copied)

18
SAP Real Time Content

You must ensure that below QA (Quality analysis) Parameters are met before
closing the ticket.

• Problem type
• Closure comments
• Closure code
• PA template

Step 8: Further information required from user

In case the consultant needs more information and cannot proceed without it, then a
mail needs to be sent to the user asking for the required information. The following
mail template needs to be used.

After sending the mail, the status of the ticket needs to be changed to “Pending
Customer”, the incident title needs to be updated with PC and the mail that is sent
needs to be pasted in the incident ticket and saved.
This is done so that any person seeing the ticket would get all the details accordingly.

Step 9: Non response of user for further information/closure confirmation.

In case the user has not responded either for further information required or for
closure confirmation:

After 2 days, then a reminder needs to be sent , marking the latest mail (i.e.,
further information/closure confirmation mail) as reminder 1. This time a copy needs
to be marked to the user’s line manager.
After 2 days on sending the reminder 1, if the user does not respond, then a
second reminder needs to be sent , marking as reminder 2. This time a copy needs to
be marked to the PFP and the concerned AS (Application specialist) also.
After 2 days on sending the reminder 2, if the user does not respond, then a
third and a final reminder needs to be sent marking as reminder3 marking a copy to all
concerned.

If still there is no response, then the following mail can be sent for inadequate
information and the ticket closed.

19
SAP Real Time Content

For no response to closure confirmation, the following template needs to be used.

Step 10: Progress update to the user

In case the ticket analysis is taking long time, then a reminder needs to be sent
to the user every 2 days on the progress.

The template to be used is as given below:

Step 11: Change ticket process

During the course of investigation or in the initial stage it is established that the
a change is required, the a related Change ticket needs to be opened.

Once it is established that a change is required, a architect approval template

needs to be filled in and sent to the onsite focal point for getting the approval.

The template needs to be in the format as given below:

Architect
approval-Template GIM30132735.doc

Once the approval is received, we proceed to open a related change ticket.

Action1: Process of opening a change ticket. Open the related incident ticket
and right click on the mouse. A menu pops up from where we can open a change
ticket. When we open a change ticket, the system asks for which category it belongs to,
in our case it would belong to either of the categories:

i) Standard/Emergency
ii) PAL4 change
We do not use the third category i.e. Downstream release.

We have 3 types of change tickets and they are:

1) Normal change ticket : These changes are those that move in a bundle. The
release management, in coordination with the change management, fix a particular date
in a month on which all the changes move into production system. A cut off date is

20
SAP Real Time Content

fixed for such changes and they need to be in Q94 (Quality) system by the cut off
date).
2) Emergency change ticket: These are those changes that cannot wait for the
bundle date, as they need to move to production immediately. Such changes are
approved in a ECAB (Emergency change approval board) meeting.
3) PAL4 change ticket: These are those changes that are pre approved and they
move once in a week to production.

Although the process for all the three types are the same, there are some slight changes
in the way they are handled.

Firstly we discuss on Normal tickets.

The change ticket has 5 phases. They are:

Assess phase
Test and Build phase
Approve phase
Implement phase
Review an close phase.

Assess phase: As soon as a change ticket is open, it is in Assess phase. The following
are the important fields that need to be filled in the assess phase.

General Tab:

a)Planned start and Planned end Date and time. In case of a bundle ticket, the bundle
dates are announced in advance and these need to be mentioned.
The time in case of a bundle ticket, Start time is always 04:00:00 and end time is
08:00:00
b)Assignment group: It should always be GLBDSXGSOFICHG
c)Assignee: Consultant handling the change.
d) The general tab needs to be filled with the following details.

e) Outage required: Should always be “No”

Description tab:

a) Reason for change: “Incident resolution other” (In case of incident tickets)
“Root cause resolution” (In case of problem tickets)
21
SAP Real Time Content

b) External change reference: Input the RT in the source field and number in the
Number field.

The details about RT is given in the next step.

c) Input the GLL link in the Change documentation URL field. The GLL for the
current year is https://sww-
knowledge.shell.com/knowhow/livelink.exe?func=ll&objId=115184744&objAction=b
rowse&sort=name.

The GLL is constant for a year.

d) Description: In the description field give the details as
Issue:
Analysis:
Resolution:
Assets tab: No action required.

Impact tab:

Impact description: Enter the data as shown below. In case you have more details as to
the financial impact, people etc. mention the same, else just input the data as shown in
the below screenshot.

Justification description: Give the appropriate justification as to why this change is

being done.

Workflow tab: All the parameters should be “No” as shown below.

22
SAP Real Time Content

Implementation tab:

a)Implementation plan: In this field, give a step by step process that you would follow
to make the changes. Include the T codes that you would be using to make the
changes.
In case of ABAP changes , kindly mention the Mod number (Mod- Modification).
This is required because if the change has to be reverted then the person reverting the
change can do so easily without having to contact the owner.

b)Backout description: In this field, give a step by step process that you would follow
to revert the changes.
c)Backout method – This should always be “Yes”
d) Backout duration: Mention the appropriate time that would be required to back the
change. Never leave this field blank.

Access/ Sign offs tab: The date conversion and the special access fields should be
always No.

Release tab:

Just click on the shown against the field “Release number”. It will populate the
release numbers, select the one for the month in which you want the change to move.
On clicking the same, all the other fields will automatically get populated.
The release number is different for each month.

Revtrac (RT) creation and processing :

23
SAP Real Time Content

RT is a tool that is used for control and movement of transport requests across the
landscape. It has an inbuilt mechanism of approval process and thus takes care of
certain SOX requirements also.

Once you go to the RT tool, click on “Create request” tab and the following screens
opens up.

The fields should be filled in as shown below.

24
SAP Real Time Content

Title:
If the change is global in nature then the title should start with GL as shown above
else, it should start with the country name i.e. GB, US and so on. The next should be
whether it is a support or a project, since all our changes are support, we will mention
as SUPP followed by the ticket number and the brief description of the change.

Class: For bundle tickets ,it should be N and for emergency changes it shld be E.
Severity: If the change is an implementation of SAP note then it has to be 1, if it is a
code change then it has to be 2 and for all other changes it has to be 3.

Production date: It should be the bundle date. Even in case of emergency changes, it
should be the bundle date.

Once this is done, save the RT, it will generate a RT number.

Now we need to add documentation to the RT. For this click of the RT, then click on
“Attachments” on the top of the screen and then click on “Create”. Then select the
required documentation that needs to be created.
The following are the documentations that need to be attached to the RT:

i) Change summary – (File type – SAP workplace)

ii) Architect approval template – (File type- PC file)
iii) Architect approval mail – ( File type – PC file)
iv) Test plan – (File type- Template)
v) Acceptance results. (File type- Template)
vi) ECAB minutes (Only for ECAB tickets)
vii) Business case (Only for ECAB minutes)

On creating an RT the first 4 documents can be attached.

All the changes need to be done in D120 (Golden client). No testing to be done
in this client. As soon as this process is complete, we can make the required changes in
the system. On saving the system would ask for the RT number and the same that we
generated earlier can be supplied.
After the development is complete, the consultant needs to sign off the RT that
the development is complete. The screen would look like this

On double clicking on Functional , it will take to the approval page. On approving, the
change moves into D110 system, ready for unit testing.
25
SAP Real Time Content

Do the unit testing and record the results in the Acceptance results sheet. Once
the results are satisfactory , you need to sign off the Unit test results complete tab.

Once this is done, the results need to be updated in the acceptance results tab.
Then a mail needs to be sent to the Architect to sign off the RT. The architect
then signs off the RT.
Once it is done, the RT moves to the acceptance system i.e. A94. Perform one
round of testing in the acceptance system. On getting satisfactory results, record the
same and sign off the RT.
The RT then moves to Quality system. Do one round of testing and request the
user to test the same. Once complete get the confirmation from the user.
Forward the same to the PFP and request him/her to sign off the RT. Once it is
done the RT is in Q-AC status.
Update all the fields in the acceptance results sheet and click on the

button in the Test script sheet. The result should be all checked
and no errors.

Similarly check in Test report sheet.

Similarly check in Test defect report sheet.

Action 2 – Change ticket: After making sure the RT is complete in all aspects as
shown above, go back to the change ticket and close the assess phase and move to the
next phase i.e.
Test and Build phase.
In this phase change the FAT contact name to TRANSPORT TOOL.
We can then close this phase and move to next phase i.e. Approve phase.
Approve phase.
In case of bundle tickets, there is nothing that needs to be changed in this phase.
At this time please fill in the SOX compliance check list and send it to the
change focal point for verification and getting further signoff from the AS.
The CTOAP also needs to be filled in and place on your desktop. Both the
templates are as given below:

SOX Checklist_16 09 CTOAP - SM7.xls

2010.xls

The focal point in turn verifies all the details and sends to the AS for approval.
The AS then approves the change ticket for asset approval and also approves the RT.
The RT then moves to Q-AR status.
26
SAP Real Time Content

Emergency change:
Change ticket: The emergency change is similar to the normal change except for the
following fields:

Assess phase:
General tab: - (i) In the “Priority” field the value should be “E” and not “N”.
(ii) In the planned start and end dates, mention the likely date the change will move
into production. The time should be 01:00:00 and 03:00:00
Description tab: - (i) Fill in the Emergency change reason and Emergency reason
comment fields.
Approval tab: (i) in this tab under the Approval Group tab – add the group –
GLBDSXGSOEAPR.
Release tab: (i) In this tab do not input any release ticket number. If it is there then
disconnect it.
RT
In the RT the “Class” should be “E”.

Once the RT is in Q-AC status, ask the PFP to give the business case. The business
case should be in the following format:

Business Case
GIM30026119 .doc

Send a mail to the change focal point to verify the RT and to get sign off from
the AS. Once AS signs off the RT, inform the PFP that the RT is now in Q-AR status
and is ready to be presented in ECAB.
Do not move the change ticket to the next phase till the change moves into
production system.
Once the change is presented in the ECAB meeting, and has been approved, the
RT will be moved to production and in P-IN status.
At this time, extract the ECAB minutes from the following link. Verify if your
RT is present in the ECAB minutes, if yes , then download the same in a word format
and attach it to the RT.

ECAB link: https://sww-

knowledge.shell.com/knowhow/livelink.exe?func=ll&objId=79051163&objAction=br
owse&sort=name&viewType=1

As you now know the exact “start and end date” now, please mention the same
in the general tab of the change ticket.
Similarly update the exact “CAB identifier” with the appropriate name i.e. EU ECAB,
AM ECAB etc. The details can be got from the ECAB minutes.

27
SAP Real Time Content

Verify if the change folder is created, the same can be verified by going through the
RT, then click on the GLL, it will open the GLL link where we find the month wise
listing, then click on the respective month and search for the change ticket number.

Click on ticket number and add the ECAB minutes and the Business case to the ticket.
Move the ticket to approve phase and fill the sox compliance Checklist and send
it to the change focal point for verification and sign off by the AS.
Once it is signed off, the ticket is handed over back to the consultant. The ticket
now needs to be sent to the change management for sign off.
Once it is signed off, the ticket is ready to be closed.
Closing steps for both Normal and Emergency tickets
In case of normal tickets after the bundle date and in case of emergency changes
or PAL4 changes after the change moves into production.
The approve phase need to be close and the Implement phase open. In this case change
the “Assignee name” to Transport tool.
Close the Implement phase and open the “Close and Review Phase” . In this
phase a new tab opens up, “Close info”.
As the change moves into production, request the user to verify the change in
production and confirm. Forward the confirmation mail to the PFP requesting him to
provide the “Production Verification Signoff” in the RT. Once it is done the RT will
move to a complete status.
In the change ticket, for “Production verification sign off” – Mention as
“Transport Tool”.
Close info tab:
Completion Code: 1.
Close Tab
Successful
Acutal
Copy from RT - In
Start Date
Production (Reduce 10 Mins)
& Time
Acutal
Copy from RT - In
End Date
Production (Actual)
& Time
Closing Change moved into
Comments production successfully

Close the ticket.

Step 12: Problem ticket: In case there is a workaround that is available and the root
cause is going to take some time, then we can close the ticket with a temporary
resolution and open a problem ticket for investigation of root cause and provide a
permanent solution.

Once the workaround is identified, then the first step to do is to open a problem ticket.
Right click on the incident ticket, then Related →Problem→ Open.

28
SAP Real Time Content

On opening a problem ticket, there are a couple of fields that need to be filled in as per
the example given below. The Target solution date should be less than the due date.

Other fields to be filled in are “Description”, “Root Cause description” and “Suggested
workaround”.
Similarly the “Assignment Group” and the “Problem Owner” needs to be filled
up. On saving, the system generates a problem ticket number. When a problem ticket
is created it is in “Open” Status and “Create, Analyze and Determine Rootcause”
phase.
On getting the number, mail the user with the details as per the format given
below and proceed to close the incident ticket. One important point to be kept in mind
is that the “Fix type” should be Temporary.

Generation of change ticket from a problem ticket:

It is not possible to create a change ticket directly from a problem ticket. For
this first a “Known error” needs to be created. For this right click on the problem
ticket then Related→ Known error→ Open.
On doing this a new ticket is created with a number starting with GKEXXXXX.
From this know error we can create a change ticket. From here on the change ticket
process will be as said before.
Closing of a problem ticket: For closing a problem ticket, a known error must be
created and the solution must be updated against the same. If there is a change ticket
associated then first the change ticket needs to be closed, then the known error and
then finally the change ticket.

If a Change ticket is associated to an incident or a problem ticket, then the change

ticket needs to be closed first and then only we need to proceed to close the incident or
a problem ticket.

Step 13 : SOX and its relevance in Shell.

SOX – Definition
The SOX legislation came into force in 2002 and introduced major changes to
the regulation of financial practice and corporate governance. It is named after Senator
Paul Sarbanes and Representative Michael Oxley, who were its main architects.

29
SAP Real Time Content

The Sarbanes-Oxley Act of 2002 (often shortened to SOX) is legislation enacted

in response to the high-profile Enron and WorldCom financial scandals to protect
shareholders and the general public from accounting errors and fraudulent
practices in the enterprise. The act is administered by the Securities and Exchange
Commission (SEC), which sets deadlines for compliance and publishes rules on are to
requirements.
Sarbanes-Oxley is not a set of business practices and does not specify how a
business should store records; rather, it defines which records be stored and for how
long.

SOX - Applicability
The legislation not only affects the financial side of corporations, it also affects
the IT departments whose job it is to store a corporation's electronic records. The
Sarbanes-Oxley Act states that all business records, including electronic records and
electronic messages, must be saved for "not less than five years."
This act is primarily applicable for those public companies that are listed on
New York Stock exchange (NYSE). Shell being a listed company has to abide by the
SOX rules and guidelines.

The following are the SOX parameters. Any failures in these is taken up very seriously
by Shell.
• Pre-Approval Emergency
• Production Verification Sign-Off
• Operational Acceptance Sign-Off
• Final Acceptance Test Sign-Off
• Test Defect Report
• Temporary Access
• Segregation of Duties

All parameters other than SOX parameters in the change ticket are FE – Functional
excellence parameters.

30
SAP Real Time Content

DELIVERBLE DOCUMENTS:

1. Question & Answer database : It is a document / Questionnaire which helps us to

gather information from our client.

2. GAP: In case of any business requirement is not supported by standard SAP is called as
a GAP.

GAP : 1 :

Target’s current process:

- Holds are placed and set up at the following levels

o Total vendor hold
o Invoice hold
o Dollar hold

Standard SAP process:

- Holds are placed and set up at the following levels

o Total vendor hold
o Invoice hold

Gap: Standard SAP does not replicate the dollar hold process. This is a manual
workload gap as well as a control gap to ensure the correct invoices are held.
31
SAP Real Time Content

Target currently uses the Vendor “Dollar Holds” process to hold newer invoices
totaling up to a set dollar amount. Only the oldest of the invoices that exceed that
amount are paid. For each pay run, the newest invoices up to a set dollar amount are
held. After the payment run, these invoice holds are systematically removed. This
process is used by Target to safeguard against vendors debit balances and is a strategic
advantage for Target. “Dollar Holds” is not a standard SAP functionality.

Below is an example:

• Invoice-1: $100 (Due on Oct/1)

• Invoice-2: $200 (Due on Oct/2)
• Invoice-3: $320 (Due on Oct/3)
• Invoice-4: $400 (Due on Oct/4)
• Invoice-5: $500 (Due on Oct/5)
• Vendor Hold limit: $1200
In this example, when the payment run on Oct/5th is processed, only Invoice-1 and
Invoice-2 are paid because they are older and they exceed the hold limit. The remaining
3 invoices (totaling $1220) are blocked during that payment run and the block is
released once that particular payment run is completed.

Background:

Data has been gathered to quantify the significance of this gap.

1. Number of invoices held:

• Below is data gathered on dollar holds for four pay runs in November 2008:
Payment Number of Dollar amount Number of
run date invoices held held vendors

November 321,896 279,382,933 1593

4, 2008

November 327,313 288,386,085 1619

6, 2008

November 303,808 304,757,444 1621

11, 2008

November 312,995 319,938,367 1619

13, 2008

Note: No expense invoices were held. This gap impacts matched invoices.

2. Estimation to manually place invoice holds:

32
SAP Real Time Content

• The data below shows four scenarios of FTE’s needed to manually place the initial
hold in SAP
Scenario Estimated Estimated number of Number of
# number of invoices held on an annual FTE’s to
invoices held basis (@ two pay runs per manually
per pay run week) place holds

1 75,000 7,800,000 18

2 100,000 10,400,000 24

3 150,000 15,600,000 35

4 300,000 31,200,000 71

• Assumptions:
- Time to update single invoice – 7 seconds (this estimate does not include
removing holds for each invoice after the pay run is complete)
- Prep time/reporting – 1.5 hours per day per team member
- Trouble shooting – 1 hour per day per team member
- Pay runs occur twice per week (if we increase the frequency of pay runs, we
would increase the count of invoices held)
• Additional report development will be required to identify invoices to hold
• Manual process also introduces additional risk compared to invoices held
systematically
3. Estimated dollar benefit of hold functionality:

• Average domestic debit balance for YTD 2008 is approximately $14M

• Target reduces the amount of debit balance accounts and the value of these debit
balances through its holds process
• Specific dollar benefit is difficult to quantify, however, increasing the dollar amount of
debit balances would have a material impact to interest lost
– Doubling the average debit balance would result in ~ $1.3M interest lost per
year @ 9%
• In addition, current holds process captures money from vendors that may never be
recovered
– YTD 2008 domestic debit balance write-offs were $2.4M
• Estimated dollar benefit in interest and write-off dollars is $3.0M annually

33
SAP Real Time Content

Option – I

Enhance SAP to include ‘Vendor Dollar Holds’. This involves development of holds logic
during the automatic payment run. This also needs creation and maintenance of vendor
dollar holds amounts in a custom table in SAP. The table needs to have company code,
vendor and dollar hold amount in it.

Benefits:

- Debit balance reduction process

- No increase to headcount
- Systematically completed holds (eliminates risk of flagging invoices manually)
- This can be applied to any vendor
Challenges/Concerns Response or Mitigation Complexity (H, M, L)

This is not standard SAP Manually place holds Medium

Option – II

Manually place invoices on hold in SAP

Benefits:

- No enhancement necessary

Challenges/Concerns Response or Mitigation Complexity (H, M, L)

Need to add team members to NA Low

accomplish this objective

Reporting enhancements NA Low

would be necessary

Accuracy risk NA Low

34
SAP Real Time Content

3. Functional Specification Document / FS / FSPEC: It is a Business requirement

document which contains objective of development that will help developers to develop
the objects.

4. Configuration documents: A document which tells how client business is mapped /

configure in SAP.

5. Business Process Procedures: List of transaction codes being used in your company.
This helps us to prepare end user manuals.

What are the enjoy transactions in SAP?

# FB50, FB60, FB70, FB65, FB75, FV65, FV75.
What is the tool you have used for preparation of end user manual?
# UPK (User Productivity Kit).

35
SAP Real Time Content

6. BPML ( Business Process Master List): It helps us to built test scenarios.

What is the tool you have used for defects management in Implementation project?
# HPQC ( HP Quality Centre).

36
SAP Real Time Content

37
SAP Real Time Content

7. BDD (Business Design Document) : The object of BDD is to document in detail scope
of business scenarios, Business Process. It insures that every body has an accurate
understanding of the final scope of the project regarding business processes,
organizational structure, system environment and project standards.

8. Test Cases: It is a Scenario to testing the Objects.

38
SAP Real Time Content

TYPES OF TESTING:
1. Unit Testing.
2. Integration Testing.
3. Regression Testing.
4. User Acceptance Testing (UAT).
5. Negative Testing.
6. Performance Testing.
1. Unit Testing: Perform testing for one object / Piece of work is called as a unit
testing.

Ex: Delete cost element, Post Vendor Invoice, Make Vendor Payment, Create GL
Master.

2. Integration Testing: Where we perform testing for more than one object is called as
a Integration testing.

Ex: - From creation of Vendor Master record to make payment.

- Purchase order to out going Payment.
- Sales order to Incoming payment.
3. Regression Testing: When we develop / configure any new objects perform testing
for existing object to check whether impacted / not is called regression testing.

Ex: New Company code & Old Company code.

When we configure settings for new company code perform testing for New
Company code.

4. User Acceptance Testing: Perform the testing by user to check whether this object
is working properly or not.

5. Negative Testing: Perform the testing with Negative values.

Ex: - Test A/R Perform testing with A/P Transaction codes.

If we develop any program for any specific company code, perform the testing
the object with another company code.

6. Performance Testing: This Performance testing has to be performed by BASIS

team, to check the system performance and to specify the time limit for execution
of programs.

39
SAP Real Time Content

AUTO CLEARING:

1. Prepare Automatic Clearing.

Path:- SPRO -> Financial Accounting (New) -> General ledger Accounting (New)
-> Business Transactions -> Open Item Clearing -> Prepare Automatic Clearing .
(TC: OB74).
➢ Click on New Entries button.
➢ Chart of Accounts : FSL.
➢ Account Key : K.
➢ From Account: 400101 to to Account: 400101.
➢ Criterion 1 : GSBER (Business Area)
➢ Criterion 2 : ZUONR (Assignment).
➢ Criterion 3 : XBLNR (Reference).
➢ Save in your request.

2. Vendor Invoice Posting – F-43

Inventory RM A/c dr 1000
Vendor A/c 1000

3. Create Open Debit – FB01.

4. Auto Clearing – F.13

➢ Company Code: FSL.
➢ Select Vendor check box.
➢ Enter Vendor A/c no.
➢ Select test run check no.
➢ Execute.
➢ Back arrow.
➢ Deselect test run check box.
➢ Execute.
➢ Ignore the message press enter.

40
SAP Real Time Content

CUT OVER ACTIVITIES

Cut Over Activities: It is nothing but free go Live activities which we are supposed to
complete before migrating the old system to SAP system.

Cut off date: The date on which we migrate from the legacy system to SAP new system.

What are the cut over activities you involved?

1. Uploading Master data (FI Related)

GL Master, Vendor Master, Customer Master, Asset Master.
2. Uploading Transactional data.
Vendor open items, Customer open items, Asset balances, GL balances.
What are the post go live activities?

1. Insure all the customizing request moved to production system.

2. Ensure that all number ranges for all the modules have been maintained in the
production system.
3. Ensure that operating concern has been generated.
4. Ensure that all master data is loaded.
5. Ensure that all transactional data is loaded.

PRE-REQUISTION:
1. We need to switch off the legacy system 3 / 4 days before go live.
2. Inform the business don’t create purchase orders, sales orders, goods receipt etc.
3. Need to create separate document types for uploading the balances ex: Vendor,
Customers.
4. Need to create some clearing accounts for data uploading.
ENTRIES:
GL (only Balance Sheet A/c’s)
G/L A/c dr
To G/L Uploading A/c
Customer:
Customer A/c (Not G/L)
To Data take over A/c
Vendor:
Data take over A/c
To Vendor A/c (Not G/L)

41
SAP Real Time Content

How did you upload GL Balances, Vendor & Customer balances?

➔ Through LSMW by using TC: FB01.
How did you upload Asset Balances?
➔ Through LSMW by using TC: AS91.

Note:
# Data take over a/c will become zero on upload of all the balances.
# When we upload legacy Asset balances it doesn’t update to the GL Accounts.

What is the transaction code to set / Reset the reconciliation a/c for Assets.
➔ TC : OAMK.

42
SAP Real Time Content

AUTHORISATION GROUPS:
1. Creation of A/R Role – TC: PFCG
➢ Path: Click on create role button from easy access screen.
➢ Role: Role for A/R (Accounts Receivable).
➢ Click on create role button.
➢ Description: Role for Accounts receivable.
➢ Click on Menu Tab.
➢ Click on Yes for the message.
➢ Add transaction button.
➢ Transaction Codes: XD01, F-22, F-28, XD02, F150, FBL5N, SU53.
➢ Click on Assign transactions button.
➢ Click on Authorizations Tab.
➢ Click on change authorizations data button.
➢ Click on yes for the message.
➢ Note: If you want to maintain Authorization at organizational element wise.
➢ Click on transfer button.
➢ You can maintain Authorization at each activity level.
➢ Click on generate button.
➢ Click on generate button once again.
➢ Note: Here automatically system generated a profile for the role.
➢ Enter.
➢ Save.
➢ Select back arrow.
➢ Click on generate button.
2. CREATION OF USER ID TC: SU01
➢ User : GANESH
➢ Select create button.
➢ Title : Mr.
➢ Last Name : P
➢ First Name: GANESH.
➢ Click on log on data tab.
➢ Initial Password: Pass@123.
➢ Repeat Password: Pass@123.
➢ Click on defaults tab.
➢ Note: Here we can change date format & Decimal format user wise.
➢ Click on roles tab.
43
SAP Real Time Content

➢ Enter the role : ARROLE.

➢ Click on profiles tab.
➢ Click on save.
➢ Go and Login.
➢ Client: 800.
➢ Userid: GANESH.
➢ Password: Pass@123.
➢ Enter
➢ Enter New password & Repeat Password.
➢ Enter.
➢ Again Press enter.
➢ Try & Check with A/P Transaction code.
➢ FBL1N
➢ We get error message you are not authorized to user this transaction code.
➢ Go to TC: SU53.
➢ Expand all the options.
➢ Note: You need to send the screen shot of SU53 to BASIS team for getting required
authorization.
3. Add new transactions code to the existing role:
➢ Go to TC: PFCG.
➢ Role : ARROLE.
➢ Click on change role button.
➢ Click on Menu tab.
➢ Click on add transaction button.
➢ Enter transaction code : FBL1N.
➢ Select Assign transactions button.
➢ Click on Authorizations tab.
➢ Click on change authorization data button.
➢ Click on yes button for the message.
➢ Click on generate button.
➢ Once again click on generate button.
➢ Save
➢ Select back arrow.
➢ Click on generate button.
➢ Once again click on generate button.
➢ Go and check authorizations for the new TC.
44
SAP Real Time Content

OSS – ONLINE SUPPORTING SYSTEM:

What is the current enhancement package implemented in your system?
➔ EPH4
To upload OSS noted in to SAP?
➔ SNOTE
OSS MESSAGE:
How to create OSS Message?
➢ Go to service.sap.com
➢ Go to click on SAP Support portol
➢ It will ask user ID & Password.
➢ Enter 2nd time also User ID & Password.
➢ Select help & Support tab.
➢ Click on Report a Product error.
➢ Click on Production system appropriate system.
➢ Enter search term ex: FS10N.
➢ Click on continue button.
➢ Click on new message / Create message.
➢ Select appropriate component button.
➢ Select Financial Accounting.
➢ Select GL.
➢ Select FI Information system.
➢ Select medium.
➢ Enter short text : FI vs MM Reports are imbalances.
➢ Enter Long Text.
➢ Click on send Message.
➢ Go and check your sent items in my inbox.
Search for OSS notes / How to view & download OSS Notes :
➢ Click on help & Support.
➢ Search for OSS notes.
➢ Enter OSS No Ex: 148757.
➢ Enter.
➢ To download the OSS notes click on PDF Document.

45
SAP Real Time Content

46
SAP Real Time Content

47
SAP Real Time Content

48
SAP Real Time Content

49
SAP Real Time Content

50
SAP Real Time Content

51
SAP Real Time Content

SAP TABLES & PROGRAMS:

1. MASTER DATA TABLES:
➢ GL, Vendor, Customer, Asset.
➢ GL- Chart of Accounts segment, Company code data segment.
➢ Vendor- General data segment, Company code data segment.
➢ Asset- Main Asset, Depreciation.

2. TRANSACTIONAL DATA:
➢ GL – Open Items, Cleared Items (Index Tables).
➢ Vendors, Customers – Open & Cleared Items.
➢ Header data Level & Line Item Level.

3. AUTOMATIC PAYMENT PROGRAM TABLES :

➢ RFGUH – Settlement data from payment program.
➢ REGUP – Processed item form payment program.
➢ REGUS – Accounts blocked by payment program.

4. MARA – Material Master.

5. INVOICE:
➢ Document Header data – RKPF.
➢ Line Item – RSEG.
6. MATERIAL :
➢ Document Header – MKPF.
➢ Line Item – MSEG.
7. CO MASTER RECORDS:
➢ Cost Center Master Data – CSKS.
➢ Profit Center Master Data – CEPC.
➢ One time document segment – BSEC.

8. CHECK INFORMATION: Payer – PAYR.

52
SAP Real Time Content

What is the TC for database Tables – TC: SE11.

How to go to tables & execute the Values.
➢ Need to list out all the GL Accounts created with the open item management.
➢ Go to TC: SE16.
➢ Enter table name : SKB1.
➢ Enter.
➢ From Menu select -> settings -> User parameters.
➢ Select field label radio button.
➢ Press Enter.
➢ From Menu select-> settings -> Fields for selection.
➢ Select open item management check box.
➢ Enter.
➢ Give Company code : 1000
➢ OI Management : Select yes (X).
➢ Just click on number of entries.
➢ Click on close button.
➢ Execute.
➢ From menu select settings -> Format list -> Choose fields.
➢ Select deselect all button.
➢ Select company code , GL Account, GL Account add text.
➢ Select copy button.
➢ From Menu -> System-> List-> Save Local file -> Select Spread sheet radio button.
➢ Enter.
➢ Save on your desktop.

PROGRAMS:
1. What if the TC to execute the Programs – SE38.
2. To Create own transaction codes – SE93.

53
SAP Real Time Content

ANLA ASSET MASTER RECORD SEGMENT

ABT1N INTERCO TRANSFER
ANLH MAIN ASSET NUMBER
AUFK INTERNAL ORDER MASTER DATA
BKPF ACCOUNTING DOC HEADER
BSAD ACOUNTG ; SECONDARY INDEX FOR CUSTOMERS (CLEARED
ITEMS)
BSAK ACOUNTG : SECONDARY INDEX FOR VENDORS (CLEARED
ITEMS)
BSAS ACCOUNTING GL ACCOUNTS CLEARED ITEMS
BSEC ONE TIME ACCOUNT DATA DOC SEGMENT
BSED BILL OF EXCHANGE FIELDS DOC SEGMENT
BSEG ACCOUNTING DOCUMENT SEGMENT
BSET TAX DATA DOC SEGMENT
BSID ACOUNTG ; SECONDARY INDEX FOR CUSTOMERS
BSIK ACOUNTG : SECONDARY INDEX FOR VENDORS
BSIM SECONDARY INDEX FOR METERIAL DOCUMENTS
BSIP INDEX FOR VENDORS VALIDATION OF DOUBLE DOCUMENTS
BSIS SECONDARY INDEX FOR GL ACCOUNTS
BSORDER PURCHASE ORDERS
BVOR INTER COM POSTING PROCEDURE
CDHDR CHANGE DOC HEADER
CDPOS CHANGE DOC LINE ITEMS
CEPC PROFIT CENTRE MASTER DATA TABLE
COBK CO OBJECT DOC HEADER
COBRA SETTLEMENT RULE FOR ORDER PRODUCTION
COEJ CO OBJECT LINE ITEMS (BY FISCAL YEAR)
COEP CO OBJECT LINE ITEMS (BY PERIOD)
COEPL CO OBJECT LINE ITEMS FOR ACTIVITY TYPES (BY PERIOD)
COFIT TOTAL RECORDS RECONCIALIATION LEDGER
CONT01_MARA CONTAINER TABLE FO R MATERIAL MASTER
CONT02_EKPO CONTAINER TABLE FOR PURCHASE ORDER ITEM
CONT02_STPO CONTAINER TABLE FO R BOM ITEM
COSP CO OBJECT COST TOTALS EXTERNAL POSTINGS
CSKA COST ELEMENTS DATA DEPENDENT ON CHART OF ACTS
CSKA COST ELEMENTS C O ACTS DATA
CSKB COST ELEMENTS DATA DEPENDENT ON CONTROLLING AREA
CSKB COST ELEMENTS CONTROLLING AREA DATA
CSKS COST CENTRE MASTER DATA
EBAN PURCHASING REQUISION
EBKN PURCHASE REQUISITION ACCT ASSIGNMENT
EINA PURCHASING INFO RECORD
EKBE PURCHASING DOC HISTORY
EKKN ACCOUNTING ASSIGNMENT IN PURCHASING DOC
EKKO PURCHASING DOC HEADER
EKPO PURCHASING DOC ITEM
GLPCA PCA ACTUAL LINE ITEMS
GLPCC TRANSACTION ATTRIBUTES
GLPCO PCA TABLE FOR ACCOUNT ASSIGNMENT TABLES
JCDS CHANGE DOC FOR SYSTEM/USERS
54
SAP Real Time Content

KNA1 CUSTOMER MASTER (GENERAL DATA)

KNB1 CUSTOMER MASTER CO CODE
KNB5 CUSTOMER MASTER DUNNING DATA
KNC1 CUSTOMER MASTER (TRANSACTION FIGURES
KNVP CUSTOMER MASTER PARTNER FUNCTIONS
KNVV CUSTOMER MASTER SALES DATA
KONH MM CONDITIONS HEADER
KONP MM CONDITIONS ITEM
LFA1 VENDOR MASTER (GENERAL DATA)
LFB1 VENDOR MASTER DATA (CO CODE)
LFBK VENDOR MASTER BANK DETAILS
LFBS VENFOR MASTER DUNNING DATA
LFC1 VENDOR MASTER (TRANSACITON FIGURES
LFM1 VENDOR MASTER RECORD PURCHASING ORG DATA
LFM2 VENDOR MASTER RECORD PURCHASING DATA
LIKP SALES DOC DELIVERY HEADER
LIKP SD DELIVERY NOTE DATA
LIPS SD DOC DELIVERY ITEM DATA
MARA MATERIAL MASTER (GENERAL DATA)
MARM UNITS OF MEASURE
MBEW MATERIAL VALUATION
MDKP MRP HEADER
MKPF MATERIAL DOC HEADER
MSEG MATERIAL DOC SEGMENT
MVER MATERIAL CONSUMPTION
PAYR PAYMENT TRANSFER MEDIUM FILE
RBCO MM INVOICE LINE ITEM
RBKP INVOICE RECIEPT - HEADER
RFBLG CLUSTER FOR ACCOUNGING DOC
RSEG DOC ITEM : INCOMING INVOICE
SCC2 EXPORTING CLIENT TO OTHER R/3 SYSTEM
SE91 MESSAGE MAINTANANCE
SKA1 GL ACCOUNT MASTER (COA)
SKB1 GL ACCOUNT MASTER (CO CODE)
SNAP TABLE FOR DUMP ANALYSIS
T000 CLIENTS
T001 COMPANY CODES
T001K VALUATION AREA
T001W PLANTS/BRANCHES
T005 COUNTRIES
T005S TAXES: REGION (PROVINCE) KEY
T006 UNITS OF MEASUREMENT
T007A TAX KEYS
T008 BLOCKING REASONS FOR AUTOMATIC PAYMENT
TRANSCATIONS
T012 HOUSE BANKS
T014 CREDIT CONTROL AREAS
T059Q WITHHOLDING TAX
T156X TRX KEY/ EVENT KEY IN M M
T80D CLIENT DEPENDENT USER EXITS
55
SAP Real Time Content

T80I CLIENT INDEPENDENT USER EXITS

T856 TRANSACTION TYPES
T880 GLOBAL COMPANY DATA (FOR KONS LEDGER)
TABW ASSET TRANSACTION TYPES
TBSL POSTING KEY TABLE
TCURC CURRENCY CODES
TGSB BUSINESS AREAS
TKA01 CONTROLLING AREAS
TSTC TABLE FOR LIST OF T CODES
TTXJ CHECK TABLE FOR TAX JURISDICTION
VBAK SALES DOC HEADER DATA
VBAP SALES DOC ITEM DATA
VBFA SD DOC FLOW DATA
VBKD SALES DOC BUSINESS DATA
VBLK DELIVERY NOTE HEADER
VBRK BILLING DOC HEADER DATA
VBRP BILLING DOC ITEM DATA
VBUP SALED DOC ITEM STATUS
T095 BALANCE ACTS FOR DEPN AREAS
GLTO GL MASTER TRANSACTION FIGURES
ANEK ASSET DOC HEADER
ANEP ASSET DOC LINE ITEM
TCURR EXCHANGE RATE TABLE
T095B GL AC VALUE ADJUSTMENT ASSET ACCOUNTING
T100C MESSAGE CONTROL
T042 PARAMETERS FOR PAYMENT RUN
REGUH SETTLEMENT DATA FROM PAYMENT PRGM
REGUP PROCESSED ITEMS FROM PAYMENT PROGRAM
REGUS ACCOUNTS BLOCKED BY PAYMENT PROGRAM
GLT0 GL ACCOUNT TRANSACTION FIGURES
T093D LAST POSTING DETAILS FOR DEPN RUN
GB01 TABLES AND FIELDS ALLOWED IN BOOLEAN LOGIC FOR
SUBSTITUTIONS
OKE6 TRANSPORT CONTROLLING SETTINGS INCLUDING MASTER DATA
VBFA SD DOC FLOW DATA

56
SAP Real Time Content

BDC – BATCH DATA CONVERSION: It is the tool. It is used to post the

transactions from Legacy system to SAP.

What is the TC to do Record the object.

➢ TC : SHBD.
➢ Click on New Recording.
➢ Recording : Test1
➢ TC : FB01.
➢ Press Enter.

I-DOCS – INTERMEDIATE DOCUMENT

Data carrying other package to SAP or Sap to other Package I doc Two types
1.Out bound process 2. In bound process.
1. Out bound process (status 1-49)
Means data carrying from SAP to other package .
2. Inbound process (status 50-75)
Data uploading from legacy system to sap
# What is the TC to see the IDoc’s List (Display)- WE02, WE05.
# How many records one I Doc contains?
1. Control Records.
2. Data Records.
3. Status Records.
1. CONTROL RECORDS: It contains which is source system, Target system, Basic
type, Partner type, Partner Number and Message type.

2. DATA RECORDS: It Contains structure and field names.

3. STATUS RECORDS: It contains message type.

# Inbound messages types.

51- Application document not posted.
53- Application document posted.
# Outbound messages types.
03 – Data passed to port OK.
02- Error passes data to port.
01- I Doc generated.

What is the TC to reprocess the IDoc?

57
SAP Real Time Content

➢ TC : BD87.
➢ Enter I Doc no :
➢ Execute
➢ Keep the cursor on I Doc.
➢ Click on Process button.

Create I Doc type from message types?

➔ BD21.
Message Types?
➔ COSMAS – Cost centre master data.
➔ COELEM – Cost element master data.
➔ PRCMAS – Profit Centre.
➔ GLMAST – GL Master record.

IDoc contains 3 records

1. Control Records. It contains which is source system, Target system, Basic type,
Message type and technical info.

58
SAP Real Time Content

2. Data Records: Contains structure and field names

59
SAP Real Time Content

3. Status Records: It contains Message Types

Inbound Message Types:
51. Application document not posted
53. Application document posted
Outbound Message Types:
03- 03 Data passed to port OK

2. WE05-IDocs List

60
SAP Real Time Content

4. BD87-Reprocess IDocs

5. BD21-

61
SAP Real Time Content

NEW GENERAL LEDGER

FEATURES IN NEW GL ACCOUNTING:

1. Segment wise reporting.

2. Parallel Currencies.
3. Parallel Ledgers.
4. Real time Integration between CO to FI.
5. Document Splitting.
6. Cost of sales Accounting.
Difference between Classical Ledger and New General Ledger.
1. If we implement new GL no need to implement profit center accounting.
2. Dummy Profit centre is no longer valid.
3. IMG navigation path also slightly different.
4. No need to maintain external numbers for depreciation posting.
What are the tables in new GL Accounting.
1. FAGLFLEXT
FA – Financial Accounting
GL – General Ledger
FLEX – Flexible
T – Total.
2. FAGLFLEXP
P – Plan line items
3. FAGLFLEXA
A- Actual line items

62
SAP Real Time Content

Define Ledgers for New GL Accounting

What is Ledger?
A Ledger is used for reporting purpose.
What is Leading Ledger?
It is based on the same accounting principle as that of the consolidation
financial statement. The leading ledger integrated with all subsidiary ledgers and
updated in all the company codes. We must specify one ledger as the leading ledger.

What is Non leading Ledger?

Non Leading Ledgers are parallel ledgers to the leading ledger the non leading
ledgers must activate company code wise for local reporting purpose.

How many currencies we can maintain to one company code?

Apart from one Local currency, we can maintain Parallel Currency.

Define and activate Non leading ledgers?

Note: First currency of non leading ledgers is always currency of the leading
ledger.

Define Ledger Groups?

What is Ledger Group?

Ledger group of a group of ledgers for the purpose of applying the same
functions and processes as a whole.

What is Representative Ledger?

The Representative ledger is used to determine the posting period and to check
whether the posting period is open / not.

If the posting period of a representative ledgers is open the system

automatically post the values in all the ledgers assigned to the group.

Even if the posting period of the non representative ledger is closed, you can
not maintain more than one representative ledger.

Note: We can maintain one representative ledger. Representative must be a leading

ledger.

63
SAP Real Time Content

NEW TRANSACTION CODES:

NEW OLD

➢ FAGLB03 FS10N
➢ FAGLL03 FBL3N
➢ FB50L FB50
➢ FAGL_FC_VAL F.05
➢ FAGLGVTR F.16

What is the path to deactivate the classic GL?

Path: SPRO-> Financial Accounting (New) -> Financial Accounting Global Settings
(New) ->
Tools -> deactivate update of classic ledger (TC: GLTO).

DOCUMENT SPLITTING
What is document splitting?
When ever there are multiple dimensions in the document system splits up the
line
item as per selected dimensions.
Ex :Invoice Expenses a/c segment 1 dr 1000
Expenses a/c segment 2 dr 1000
To Vendor a/c 2000
General ledger view in document splitting
Expenses a/c segment 1 dr 1000 Active
To Vendor a/c segment 1 a/c 1000 Splitting
Expenses a/c segment 2 dr 1000
To Vendor a/c segment 2 a/c 1000

Payment :
Vendor a/c dr 2000
To Bank a/c 2000
Document splitting in general ledger view.
Vendor a/c dr segment 1 1000
To Bank a/c segment 1 1000 Passive
Vendor a/c dr segment 2 1000 Splitting
To Bank a/c segment 2 1000

64
SAP Real Time Content

Classify GL Accounts for document splitting:

➢ Chart of Accounts : FSL.
➢ Classify G/L accounts for document splitting.1
➢ Classify document types for document splitting.
➢ Define zero balance clearing account?

What is zero balance clearing account?

When we activate zero balance clearing account system checks whether the

balance of account assignment object is zero after document splitting. If it is not

matched / If it is not “0” the system post the variance amount to zero balance

account.

➢ Define document splitting characteristics for general ledger accounting?

➢ Activate document splitting?

➢ Postings.

65
SAP Real Time Content

Purpose / Objective

The Purpose of the document is to provide High Level Overview of the New Generic
Ledger

(G/L) features available in SAP ECC 6.0. The following topics are covered in the same:

1. New GL Accounting – Overview

2. Document Splitting Concept
3. Segment Reporting
4. Parallel Ledger Concept
5. Real time Integration of CO with FI
6. Reporting as per cost of sales accounting
7. Post capitalization of cash discount to Assets
8. Changes in ECC 6.0 from earlier versions

1. Overview
The new general ledger in SAP ERP has the following advantages over the classic
general ledger

A. The new general ledger has an extended data structure as standard, as opposed to the
classic totals table GLT0. Customer fields can also be added to the general ledger table
FAGLFLEXT
B. The 'Segment' (AS-17) entity and the relevant reporting that are required for segment
reporting according to IAS and U.S. GAAP are available in the new General Ledger.
C. When you use the new 'Document Splitting' function (online split), you can create
financial statements at company code level and, if required, for entities, such as the segment.
For each document, the system then creates a zero balance for the relevant entity, for
example, for the segment.
D. As a result, you no longer have to carry out time-consuming reconciliation tasks between
FI and CO for the end of period since cross-entity processes are transferred in real-time to
the new General Ledger in Controlling. Furthermore, you can, for example, navigate from
the financial statements report results or the profit and loss statement report results to the
relevant CO report.
E. The new General Ledger uses the same interfaces as the General Ledger in R/3. As a
result, users do not require any additional training.
F. Due to the new 'multi-dimensional' aspect in the General Ledger, all data that is relevant
for the General Ledger is stored in one environment. As a result, reconciliation tasks, for
example, between the general ledger and Profit Center Accounting or the consolidation
staging ledger, and processing steps that have to be carried out repeatedly in the individual
applications (for example, balance carry forward) are no longer required. When you use the
new General Ledger, you may not have to use the special ledger anymore.
G.Accelerated closing: The elimination of additional periodic splitting programs
significantly speeds up the closing process. Subsequent closing processes, such as foreign
currency valuation, may be executed immediately.

66
SAP Real Time Content

New General Ledger Accounting Advantages

1 Segment Reporting

2 Legal Entity Reporting

3 Parallel Accounting

4 Management Reporting

5 Balanced Books in any dimension

6 Total Cost of Ownership reduction

7 Fast closing for Month End Activities

2. New G/L Accounting Document Splitting Concept

Document splitting is an essential tool for drawing up complete financial statements
for the selected dimensions (e.g. SEGMENT, PROFIT CENTER, BUSINESS AREA or
customer field) at any time.

Document splitting splits up line items during the posting for selected dimensions such
as receivable lines by PROFIT CENTER or BUSINESS AREA. Also, to affect a zero
balance setting in the document for selected dimensions such as SEGMENT, document
splitting can be used. The zero balance setting may generate additional clearing lines in
the general ledger view. Entry view is based on table BSEG as used in classic g/l. G/l
view is based on the new g/l tables.

You can choose between displaying the document either in its original form in the
entry view or with the generated clearing lines from the perspective of a ledger in the
general ledger view.

The online splitting function is available for customer-defined and industry-specific

fields. And it can be applied not only to individual documents but throughout the entire
document chain. The advantages of the online splitting function include:

Extensibility and flexibility: Because my SAP ERP allows you to add new fields, you
can create management reports, supplementary balance sheets, and profit-and-loss
statements for industry-specific and enterprise-specific purposes.

Increased data quality: In my SAP ERP, the results of the document split are visible in
the document itself. This eliminates the need for additional check steps in alternative lists
and improves data quality.

Document splitting – Example (1) – Active splitting

67
SAP Real Time Content

This entry shows how expenses account’s cost center and its relative profit center is
automatically derived into the vendor account through online active splitting functionality

Example 1: Invoice

Suppose a vendor invoice containing the following items is entered:

Posting Key Account Cost center Profit center B. Area Amount

31 Payable -100

40 Expense CC1 PC1 1030 40

40 Expense CC2 PC2 6030 60

Document splitting then creates the following document in the General Ledger view:

Posting Key Account Cost center Profit center B. Area Amount

31 Payable CC1 PC1 1030 -40

31 Payable CC2 PC2 6030 -60

40 Expense CC1 PC1 1030 40

40 Expense CC2 PC2 6030 60

Example 2: Payment against invoice

The payment for the above vendor invoice then contains the following items when
entered:

Posting Cost Profit B. Amou

Account
Key center center Area nt

50 Bank -95

25 Payable 100

Cash
50 -5
Discount

This is the payment entry for the previous vendor invoice. Even though, no profit
center provided to the Bank or vendor account during payments, but it derives the profit
center from the vendor invoice and will be updated in the GL view.

68
SAP Real Time Content

Posting Key Account Cost center Profit center B. Area Amount

50 Bank CC1 PC1 1030 -38

50 Bank CC2 PC2 6030 -57

25 Payable CC1 PC1 1030 40

25 Payable CC2 PC2 6030 60

50 Cash Discount CC1 PC1 1030 -2

50 Cash Discount CC2 PC2 6030 -3

BRITANNIA INDUSTRIES LIMITED currently executed Business area wise Trail

Balance only at the end of the month.

Month end activities:

1. F.50 – Profit and Loss adjustment

2. F.5D - Calculate Balance sheet adjustment
3. F.5E – Post Balance sheet adjustment
Advantages in New GL: No need to execute above transaction on monthly base, based
on document splitting it will update Business area online and we can run Trail Balance at
any time no need to wait for month end.

3. Segment Reporting in New G/L Accounting

The segment field is one of the standard account assignment objects available in
SAP to run analysis for “objects” below company code level. Segments can be used to meet
international accounting rules (namely IAS /IFRS /US GAAP).

It simplifies the reporting options in the new general ledger and eliminates the
requirement of having a separate PCA /special purpose ledger. This has also helped in
reducing many complex month end transactions like balance sheet re-adjustment, transfer
of payables /receivables in PCA etc. As per International Financial Reporting Standards
(IFRS) reporting financial information by line of business and by geographical area, which
is know n as segment reporting compliance can be met in SAP through Segment
functionality.

The 'Segment' (AS-17) entity and the relevant reporting that are required for segment
reporting according to IAS and U.S. GAAP are available in the new General Ledger.

Segment Derivation:

•Derive through profit center by assigning in profit center master data.

•Passing a JV using segments (directly assigning the segment at document processing

level itself)

• Derive through BADi (FAGL_DERIVE_SEGMENT) without profit center activation

69
SAP Real Time Content

Business area Vs Profit center/Segment

Business area is an organizational unit which corresponds to the specific business

segment or area of responsibility. Identification of business area helps in segment reporting of
a company in its financial statements. Business areas can be identified based on the products
of the company or based on geographical area.

The objective of business area is more for reporting purposes whereas profit center
allows to analyses areas of responsibility and to delegate responsibility to decentralized units
(e.g., the various divisions within a company). Thus, profit center are basically treated as
"companies within a company" and ensures effective control.

Profitability Segment corresponds to market segment. The market segments can be

defined as products, product groups, customers, customer groups, geographic areas, etc. For
example, a company may wish to analyze profitability for a specific group of products that
the company sells to a particular customer (or group of customers). When setting up CO-PA,
the company will have broad flexibility to choose whichever characteristics are relevant for
defining the company's market segments. Each unique combination of characteristic values
(e.g. sales of product A to customer X) defines a profitability segment.

Main distinguish factor is that distribution and assessment is possible in profit center
but not in business area.

One more distinction is that Business area need not be attached to any organization
structure. But profit centers can be created only under the controlling area. Business area can
be across controlling area.

Business area concept is used for making strategic decisions by the management
whereas the primary purpose of profit centre accounting is responsibility accounting.

BRITANNIA INDUSTRIES LIMITED currently executing KE30 – Brand wise profitability

analysis report but it gives only 90% accurate report.

Example: Primary fright value always updates plan values

New General Ledger we can get 100% accuracy and also we can get multi dimensions i.e.
Products, product groups, customers, customer groups, geographic areas etc

4. New G/L Accounting Parallel Valuation: Parallel Ledger Concept

Parallel financial reporting:

1. Parallel financial reporting means that a company's financial statements have to be created
in accordance with different accounting rules. This is because a local view is no longer
sufficient in a globalized world of creditors (banks, shareholders) and business partners. An
internationally recognized account standard is increasingly in demand.

70
SAP Real Time Content

2. Examples of internationally recognized accounting rules include:

- IAS/IFRS

- US GAAP

3. Parallel valuation approach can be modeled in three ways in SAP:

- Creating a different company code for different valuation approach

- Creating additional GL accounts in the same Chart of Account

- Creating Parallel ledgers using same GL accounts in COA – also called as ledger
solution in SAP

Following IFRS standards are applicable to FMCG industry:

• Inventory

• Long-lived assets

• Mass asset accounting

• Decommissioning liabilities

• Intangible assets

• Leases

• Revenue Recognition

• Segment Reporting

Parallel Valuation – Ledger concept:

New General Ledger accounting uses the ledgers known from the application component FI-
SL to save totals values. It consists of two ledgers, namely:

- Leading Ledger

- Non Leading Ledger

Leading Ledger:

For each client, there is a leading ledger to which all company codes are assigned. This ledger
should contain the group valuation view. Leading ledger is based on the same accounting
principle as that of the consolidated financial statement. It is integrated with all subsidiary
ledgers and is updated in all company codes. It automatically receives the settings that apply
to the company code like the local currency (and also additional currencies) that are assigned
to the company code, uses the same fiscal year variant and posting period variant that are
assigned to the company code.

71
SAP Real Time Content

Non Leading Ledger:

We can also create additional ledgers called as non-leading ledgers for each company code.
By having different characteristic values and fiscal year definitions, these additional ledgers
can be used for different purposes, such as for parallel accounting or for management
reporting. In short, non leading ledgers are parallel ledgers to the leading ledger. We can use
these different ledgers, for example, to model different accounting rules for parallel valuation

Example: Leading Ledger – Local GAAP requirement and Non leading ledger – US GAAP
or IAS or UK GAAP.

BRITANNIA INDUSTRIES LIMITED MIS (different financial report) report prepared in

Excel sheet

All MIS report we can prepare in SAP itself based on activation on non-leading ledger

5. Real Time Integration of CO with FI

During allocations in Controlling, most of the postings created do not affect Financial
Accounting. These postings do not update any G/L account transaction figures; they are
postings within Controlling. If, however, an allocation in Controlling leads to a change in the
functional area or any other characteristic (such as Profit Center or Segment) that is relevant
for evaluations in Financial Accounting, a shift occurs between the affected items in the profit
and loss statement. For this reason, this information has to be transferred to Financial
Accounting. This reconciliation between Controlling and Financial Accounting takes place by
means of real-time integration.
As a result of real-time integration, all Controlling documents that are relevant for
General Ledger Accounting are transferred from Controlling to General Ledger Accounting
in real time. This means that Financial Accounting is always reconciled with Controlling.
A document is created in Financial Accounting for each posting in Controlling. This means
that the detailed information contained in the CO documents is always available in reports in
New General Ledger Accounting. This information can be sorted by the following, for
example:
● Functional area
● Cost center
● Internal order
BRITANNIA INDUSTRIES LIMITED not activated reconciliation ledger in current system
and we can not able to transfer CO settlement document to FI

Example:

An internal order for business area 1030 is settled to a cost center of business area 6030. The
document from this allocation is not transferred in real time to Financial Accounting.
Mismatch between FI & CO could be eliminated

72
SAP Real Time Content

6. Reporting as per Cost of Sales Accounting

Cost of sale accounting (Functional area):

The profit and loss statement of an organization can be created according to two different
procedures:

Period accounting
Cost of sales accounting
Cost of sales accounting compares the sales revenue for an accounting period with the
manufacturing costs of the activity. The expenses are allocated to the commercial functional
areas (manufacturing, sales and distribution, administration, and so on). Expenses and
revenues that cannot be assigned to the functional areas are reported in further profit and loss
items, sorted according to expense and revenue type.
With this type of grouping, cost of sales accounting identifies where costs originate in a
company. It therefore portrays the commercial purpose of the expense
Functional area:

A functional area is an account assignment characteristic that sorts operating expenses

according to functions. For example:

Production
Administration
Sales
Research and development
Deriving Functional area:

To sort expenses according to corporate functions, the system derives the functional area for
the following postings:

Primary postings (postings in Financial Accounting) to a profit and loss account

Secondary postings (allocations in Controlling)
The functional area is derived for both objects involved in the allocation.
In the following cases, no functional area is derived:
Postings to balance sheet accounts
Entry of statistical key figures in Controlling

BRITANNIA INDUSTRIES LIMITED prepared only period accounts, not activated cost
of sale account wise
New General ledger we can generate profit and lose statement with reference to cost of sale
account. We can match the sales revenues to the cost involved in making the revenue
e.g. manufacturing cost, Sales and Distribution cost, R&D and Management.

73
SAP Real Time Content

Benefited users: Across Organization wide in BRITANNIA INDUSTRIES LIMITED,

Specially Costing, Supply Chain and MIS Team.

7. Post Capitalization of Cash Discounts to Assets

The activation of the "Post-Capitalization of Cash Discount to Assets" has the effect that the
cash discount of an asset-relevant payment is not posted to the cash discount account, but
directly to the asset account.

Post capitalization of cash discount to assets – Example

1. F-90 invoice created for purchases asset direct form Vendor

Line item Posting key Account B. Area Amount

1 31 Vendor 1030 -116000

2 70 Asset 1030 100000

3 40 Input Tax 1030 16000

2. F-53 Payment to Vendor

Line Posting B. Amoun

Account
item key Area t

1 50 Bank 1030 -112520

Cash Discount but not

2 75 Asset 1030 -3000
capitalized

3 25 Vendor 1030 116000

input
4 50 1030 -480
Tax

Cash discount: In many countries cash discount reduces the acquisition and production costs
of the asset.

BRITANNIA INDUSTRIES LIMITED now we have to execute a report SAPF181 at end of

month to adjust the acquisition and production costs

New General Ledger it will adjust automatically based on Document splitting

Asset Explorer – Display Asset value – AW01

Asset Value date Amount Transaction type Transaction name

01.04.2010 100000 100 External Asset Acquisition

01.04.2010 -3000 100 External Asset Acquisition

74
SAP Real Time Content

Total Asset Value 77000

8. Changes in ECC 6.0 from Earlier versions

1. Customization changes

Additional nodes added in FI customization – an overview:

• Profit center and Segments: Customization -> Enterprise structure -> Definition –> Profit
center and Segment.

• Ledgers: Customization -> Financial accounting (New) -> Financial accounting global
settings (New) -> Ledgers.

Mainly useful for parallel accounting through parallel ledgers.

• Real time integration of CO with FI: Customization -> Financial accounting (New) ->
Financial accounting global settings (New) ->

Real time integration of controlling with financial accounting.

• Extended Document splitting: Customization -> Financial accounting (New) -> General
ledger accounting (New) -> Business Transactions -> Document splitting and extended
document splitting.

• FI level planning: Customization -> Financial accounting (New) -> General ledger
accounting (New) -> Planning.

This is a replacement for FI-SL level planning

• FI level allocations: Financial accounting (New) -> General ledger accounting (New) ->
Periodic processing -> Allocation.

This is a replacement for FI-SL level allocation.

2. Front end changes

New transaction codes / replacement of old transaction codes – and overview:

• Balance carry forward transaction code for GL is FAGLGVTR

In the place of F.16

• Foreign currency valuation transaction code is FAGL_FC_VAL

In the place of F.05

• Regrouping its FAGLF101

In the place of F101 -

75
SAP Real Time Content

• Financial statement version transaction code is S_PL0_86000028

(a new Drilldown reporting).

• GL wise line item display – FAGLL03 (similar kind of functionality as FBL3N except
drilldown option, but ledger wise line item display can be possible)

• GL wise balance display – FAGLB03 (similar kind of functionality as FS10N, but ledger
wise GL balance display can be possible)

• During simulation of a document, we can also find “Simulate in General

Ledger” which mainly displays the entire split of related account assignments

3. Eliminated closing activities in New GL

Examples of eliminated closing activities in New General ledger – an overview:

• Transaction KALC is no longer available (by default) after New General Ledger Accounting
has been activated – an information message points out the new real-time integration between
CO and FI.

• Balance sheet adjustment (=> SAPF180 or transaction codes F.5D and F.5E – example for
creation of business area balance sheets)

• Profit and Loss adjustment (=> SAPF181 or transaction code F.50 – example for post
capitalization of cash discounts)

• Maintenance and use of the various FI-SL ledgers (=> SAPF180A +

Transaction codes 1KEH, 1KEI, 1KEJ, 1KEK and 1KE8).

76
SAP Real Time Content

SAP QUERY

How to write query?

QUERY: Need to extract the GL Accounts?

Company Code
GL Account SKB1
Reconciliation Account
Description - SKAT
➢ Go to TC: SQVI.
➢ Quick View : TEST1.
➢ Click on create button.
➢ Title : GL Accounts with description.
➢ Data source : Table join.
➢ Select basis mode radio button.
➢ Press enter.
➢ Click on insert table.
➢ Table : SKB1.
➢ Enter.
➢ Click on insert table.
➢ Table : SKAT.
➢ Enter
➢ Select back arrow.
➢ Select required fields.- Company code, GL A/c, Account is recon from
company code segment
➢ Select account long text from chart of accounts.
➢ Click on selection fields tab.
➢ Select company code from possible selection fields.
➢ Save.
➢ Execute.
➢ Company Code: FSL.
➢ Execute.
➢ Select Back arrow.
➢ Select Language Key, Account is Recon A/c
➢ Save.
➢ Execute.

77
SAP Real Time Content

INTEGRATION:

FI TO MM:

1. PLANT CREATION: Plant means where materials are produced or goods and
services are provided.

2. DEFINE DIVISION: Ex: Steel / Cement.

3. MAINTAIN STORAGE LOCATION: A place where Stock is physically kept with

in a plant. Storage Location – Plant Specific.

Note : # One plant can have multiple storage location.

# One storage location can have only one plant.
4. MAINTAIN PURCHASING ORGANIZATION: It is responsible for all
purchasing activities with in the organization.

Note : # One plant can have one purchase organization.

# One purchase organization can have multiple plants.
5. ASSIGN PLANT TO COMPANY CODE:
Note : # One plant can be assigned to one company code.
# One company code have multiple plants.
6. ASSIGN BUSINESS AREA TO PLANT / VALUATION AREA & DIVISION:
Valuation area is a place where the material is valuated. It can be a company code /
Plant.
7. ASSIGN PURCHASING ORGANIZATION TO COMPANY CODE:
Note : # One purchasing org can assign only one company code.
# One company code have multiple purchasing organization.
8. ASSIGN PURCHASING ORGANIZATION TO PLANT:
Note : # One purchasing organization can assign multiple plants.
# One plant can have multiple purchasing organization.
9. CREATE PURCHASING GROUPS: Responsible team for procuring raw material.

10. DEFINE MATERIAL GROUPS: ex: Chemicals, Textiles.

11. MAINTAIN COMPANY CODES FOR MATERIAL MANAGEMENT:

Allowed posting to previous period:

If we want to allow the system to Post the transaction to previous period – Select
ABP.
Disallowed back posting after a period change:
If this indicator is set the indicator allowed posting to pervious period is not set
automatically during period closing.
78
SAP Real Time Content

12. DEFINE ATTRIBUTES OF MATERIAL TYPES:

Material Types: # It is like a Account group in FI.
# It classifies the material master record.
Where did you maintain the price control?
➔ At material type level.
What is price control?
➔ It can be a moving average price / Standard price.
What is the price control we followed?
➔ Raw material – Moving average price, Finished
goods- Standard price.
13. SET TOLERANCE LIMITS FOR PRICE VARIANCE FOR PURCHASE
ORDER:
When we create PO system checks the price entered in the PO item with
price stored in the material master record. If the defense amount is with in tolerance
amount / limits system will allow the postings. If the variance exceeds the tolerance
limits the system issues the warning / error message.

14. PLANT PARAETERS.

15. TOLERANCE LIMITS FOR GOODS REEIPTS:

When we receipt goods system checks each item to determine whether

the goods receipt variance from the purchase order / the material master data.

16. MAINTAIN DEFAULT VALUES FOR TAX CODES

17. SET TOLERANCE LIMITS FOR INVOICE VERIFICATION

When we do Invoice verification system checks each item for differences

between the invoice receipt and the purchase order goods receipt.

18. DEFINE AUTOMATIC STATUS CHAGE

19. GROUP TOGETHER VALUATION AREAS:

Valuation group code is a group of valuation areas. It makes easier to set

automatic account determination.

20. DEFINE VALUATION CLASS:

Valuation class is used to assign GL Accounts for automatic postings.

Valuation class assigned in material master.

What is Valuation Modifier?

79
SAP Real Time Content

It is nothing but group of valuation areas, which helps us to maintain

automatic account assignment.
What is General modifier?
It is used for offsetting transactions Ex: Raw material consumption, delivery
etc.
What is Movement type?
It is similar to postings keys in FI. It specify the movement of materials.
Ex: Issuing, Material receipt etc.
What is transaction Keys?
It is used to assign automatic account assignment ex: BSX, WRX.
What id GBB?
It is used for offsetting transactions.

FI TO MM PROCESS FLOW / PROCUREMENT CYCLE / P TO P:

1. Material acquisition (By production dept to stores).
2. Purchase acquisition (By stores to purchase dept).
3. Call for enquiries- Get quotations & Price comparisons (By purchase dept).
4. Creation of Purchase order- In purchase order we mention vendor master record,
Material master record, Quantity, Rate, Terms & Conditions etc. – TC: MV21.
5. Goods Receipt: Goods receipt will be done with reference to PO. The flow of
accounting entries starts form goods receipt – TC: MIGO.
Inventory RM a/c dr 1000
To GR/IR clearing a/c 1000
6. Invoice Verification: It will be done with reference to goods receipt TC : MIRO
GR/IR Clearing a/c dr 1000
To Vendor a/c 1000
7. Out going payment
Vendor a/c dr 1000
To Bank a/c 1000

What is GR/IR Clearing account?

# GR – Goods receipt # IR- Invoice Verification
It is a temporary offsetting account some times we may receive goods
before invoice, some times we may receive invoice before goods receipt.
This account has to be managed with open item management. At the end
of month / Point the balance in GR/IR clearing account must be “0”.

80
SAP Real Time Content

FI TO MM CUSTOMIZATION FLOW:
1. We need to create accounting category references for material master record in
TC: OMSK.
2. We need to assign accounting category references to valuation class.
3. Also we need to assign accounting category reference to material type.
4. By using the material type we create material master record.
5. In material master record we need to specify valuation class.
6. To Valuation class we need to specify the account determination with the
combination of valuation modifier and general modifier.
7. By using the material master created, we using purchase order.
8. In purchase order we need to specify material master record, vendor master
record, quantity, rate and payment terms.
9. By using PO goods receipt will be done.
Inventory a/c dr 1000 – Qty x rate from PO – BSX
To GR/IR Clearing a/c 1000- WRX
10. Invoice verification will be done with reference to GR.
GR/IR clearing a/c dr 1000 – Qty x Rate
To Vendor a/c 1000 – From PO
Raw material consumption:
RM Consumption a/c dr 500 – Qty x Rate – GBBVBR
To Inventory RM a/c 500 – BSX
Production receipt:
Finished goods a/c dr 1000 – Qty x Rate from PO – BSX
To Inc / Dec in stock a/c 1000 – GBB
Delivery:
Cost of goods sold a/c dr 1000 – Qty x Rate from sales order – GBB
To Finished goods a/c 1000 – BSX
Billing:
Customer a/c dr 1000
To sales a/c 1000
Where do you assign valuation class in material master record?
➔ In Accounting 1 View.
Where do you assign profit centre in material master record?
➔ In Costing 1 Tab.

81
SAP Real Time Content

TRANSACTION KEYS:
➢ BSX – For Inventory postings.
➢ WRX – For goods receipt & Invoice receipt.
➢ GBB – For offsetting transactions.
✓ VBR – Consumption
✓ ZOF – Production receipt with out production order.
✓ AUF – Production receipt with production order.
✓ VAF - Delivery where revenue a/c created as a cost element / Sales
a/c.
✓ VAX – Delivery where sales a/c not created as a revenue a/c.
How many payment terms we can assign in vendor master record?
➔ We can assign 2 payment terms.
1. At Company code segment.
2. Purchasing organization segment.
What is the differences between payment terms assigned in company code
segment &
Purchase organization segment?

If invoice is generated with out PO from FI payment terms will be

Extracted from the company code segment. If invoice is generated with PO
form MM
Purchasing organization segment payment terms will be extracted.
What is the transaction code to see material document?
➔ MB03
To see stock ledger?
➔ MB5B
SCENARIOS:
1. Moving average price – Full stock is available
PO Qty : 10 , Rate : 10
GR 10 x 10 = 100
IR 10 x 11 = 110
GR – Inventory RM a/c dr 100
To GR / IR clearing a/c dr 100
IR – GR / IR clearing a/c dr 100
Inventory RM a/c dr 10
To Vendor a/c 110

82
SAP Real Time Content

2. Moving average price – No stock is available

PO 10 x 10 = 100
GR 10 x 10 = 100
IR 10 x 11 = 110
GR – Inventory RM a/c dr 100
To GR/IR clearing a/c 100
IR – GR/IR Clearing a/c dr 100
Price difference a/c dr 10
To Vendor a/c 110
3. Moving average price – Partial stock is available.
PO – 10 x 10 =100
GR – 10 x 10 = 100
IR – 10 x 11 = 110
GR – Inventory RM a/c dr 100
To GR/IR Clearing a/c 100
IR – GR/IR Clearing a/c dr 100
Price Differences a/c dr 5
Inventory RM a/c dr 5
To Vendor a/c 110
FI TO MM ACCOUNTING ENTRIES WITH EXCISE:

GR – Inventory RM a/c dr 100

To GR clearing a/c 100
CENVAT a/c dr 10
To CENVAT clearing a/c 10

IR- GR/IR clearing a/c dr 100

CENVAT Clearing a/c dr 10
VAT Receivable a/c dr 5
To Party a/c 115.

83
SAP Real Time Content

FI TO SD INTEGRATION:
1. DEFINE REGION: Region means area Ex : AP, Karnataka.

2. DEFINE SALES ORGANIZATIONS: It is an organizational element in SD

module and its responsibility for selling material & Services.

3. DEFINE DISTRIBUTION CHANNEL: It means how we are going to distribute

materials and services to end users.

4. DEFINE SHIPPING POINT: It is a part of company responsible for type of

shipping materials. It is a place where shipping / Transport of materials.

5. ASSIGN SALES ORGANIZATION TO COMPANY CODE:

# One company code can have multiple sales organization.

# One sales organization can have only one company code.
6. ASSIGN DISTRIBUTION CHANNEL TO SALES ORGNIZATION:
# One sales organization can have multiple distribution channel.
# One distribution channel can have to assign multiple sales organization.
7. ASSIGN DIVISION TO SALES ORGANIZATION:
# One sales organization can have multiple division.
# One division can have multiple sales organization.
8. SET UP SALES AREA: It is a combination of sales organization distribution
channel and division.
9. ASSIGN SALES ORGANIZATION DISTRIBUTION CHANNEL – PLANT
10. DEFINE RULES BY SALES AREA.
11. ASSIGN SHIPPING POINT TO PLANT:
# One plant can have multiple shipping point.
# One shipping point can assign to multiple plant.
12. DEFINE COMMON DISTRIBUTION CHANNEL
13. DEFINE COMMON DIVISIONS
14. MAINTAIN PRICING PROCEDURE: It is a defines how values to be posted
in SAP.
15. DEFINE PRICING PROCEDURE DETERMINATION
16. DEFINE TAX DETERMINATION
17. SET UP PARTNER DETERMINATION
18. ASSIGN SHIPPING POINTS.

84
SAP Real Time Content

FI TO SD PROCESS FLOW / OTC ( ORDER TO CASH FLOW)

➢ Enquiry.
➢ Request for quotations.
➢ Quotations.
➢ Sales order.
➢ Delivery.
➢ Billing.

FI TO SD CUSTOMIZATION FLOW:

1. In VKOA transaction we have to specify revenue account determination.

➢ Application area – V – Sales & Distribution.
➢ Condition Type – KOFI – Accounting determination.
➢ Chart of Accounts – FSL.
➢ Sales organization – FSLP.
With the combination of account assignment group for customer
master record whether domestic / Foreign account assignment group for
material master record to the accounting key ERL (Revenue).
2. The accounting key ERL is assigned to condition type – PR00.

3. The condition type PR00 is maintained in pricing procedure.(ovkk)

4. The pricing procedure assigned to customer master record, sales document type
and billing document type.

5. The account assignment group for customer has to be assigned in customer master
record. Account assignment group for material master record has to be assigned to
material master record.

6. By using this customer master record & Material master record we create sales
order –VA01. Note: No accounting entry will be generated at the time of sales
order creation.

7. Delivery will be done with reference to sales order – VL01.

Cost of goods sold a/c dr 5000 – Qty x Rate from sales order- GBB VAY

To Finished goods a/c 5000 – BSX.

85
SAP Real Time Content

How to do revenue account determination analysis?

➔ Note : When billing document was created no accounting document created.

➔ Go to TC : VF02 give the billing document no from menu select environment

-> Account determination -> Analysis ->Revenue Accounts-> Expand the
condition type PR00.

At what level COPA document will be generated?

➔ At the time of billing document creation.

How billing document / SD Document to COPA assigning value fields to

condition type – KE4I.

86
SAP Real Time Content

LSMW: (LEGACY SYSTEM MIGRATION WORK BENCH)

It is a tool which is used to upload master data and transactional data in

to SAP from legacy system.

Methods Available in LSMW:

1. Standard batch / Direct input method.

2. Batch Input recording method.
3. Business object method (BAPI).
4. I Doc (Intermediate document).

BDC: (BATCH DATA CONVERSION)

It is a program which is used to upload master data as well as

transactional data in to SAP from legacy system.

What are differences between LSMW & BDC?

LSMW & BDC are used to upload the master data as well as
transactional data into SAP from legacy system.

# LSMW is used to upload straight forward data.

# BDC is used to upload the data with multiple conversions and formulas
in to SAP system.

87
SAP Real Time Content

VALIDATION:

It is a process of checking values and the combination of values entered

into the system.

The entered values are checked against a user pre defined values. If the
statement is true system will allow you to post the data. If the statement is false
system issue message defined by user.

Path: SPRO-> Financial Accounting (New) -> Special purpose ledger ->Tools ->
Maintain validation / substitution/ Rules -> Maintain Validation (TC: GGB0)

ACTIVATE VALIDATION FOR YOUR COMPANY CODE:

Transport request is generated only at this step.
Path: SPRO-> Financial Accounting (New)-> Financial Accounting global settings
(New) -> Tools -> Validation / Substitution-> Validation in accounting document

(TC: OB28).

At What level we can write validation?

➢ Document header level.

➢ Line item level.
➢ Complete document level.
What is the TC to create sets : GS01.

3 STEPS IN VALIDATION:
1. Prerequisite.
2. Check.
3. Message.
SUBSITUTION (GGB1)
At what level we can write substitution
1 Document header level
2 Line item level
3 Complete document level
4 Cost of sales account level
2 STPES IN SUB-STITUTION
1. Prerequisite
2. Substitution

88
SAP Real Time Content

Call up points or validation substitution call up point

call up points are specific places in an application that specify exact location where
validation /sub situation occurs . if you want valuate or substitute a values you must
activate validation or substitution for call up point for which you want the validation or
substitution occurs.
Call up points
At what level we can create write call up points
0001 Document header level
0002 Line item level
0003 complete document level
0004 cost of sales account level

89
SAP Real Time Content

HOW TO TRANSPORT VALIDATION :

Path: SPRO -> Financial Accounting (New)-> Special purpose ledger-> Tools -
> Transport -> Transport Validation (TC : GCT9).

➔ Select validation name : ASBA.

➔ Select all the check boxes and execute.
➔ Click on create request button.
➔ T2 for validation.
➔ Press enter.
Note : Message and message class are not transferrable. We have to created
manually.

90
SAP Real Time Content

91
SAP Real Time Content

92
SAP Real Time Content

BAPI (BUSINESS APPLICATION PROGRAMMING INTERFACE).

➢ TC : SE37.
➢ Function module : BAPI_ACC_DOCUMENT_POST.
➢ Execute.
➢ Click on document header value button.
➢ Company code : FSL.
Document date : 01.11.2011 Maintain data
Posting date : 01.11.2011 For required fields.
Fisc year : 2011
Document type : SA
Header Text : ABC
➢ Select back arrow.
➢ Click on account GL Account.
➢ Item No: 01
GL Account : 400100
Item text : Test data
Business area :
Cost centre : Department A
➢ Click on new line button.
➢ Item No :02
GL Account : 200100
Item Text : Test data
Value date : 01.11.2011
Text :
➢ Select back arrow
➢ Click on currency amount details.
➢ Item No : 1
Currency : INR
Amount : Enter amount with out (-) sign (1000)
Item No :2
Currency : INR
Amount : 1000
➢ Select back arrow.
➢ Execute.
➢ Go and check the status details under return details.

93
SAP Real Time Content

CENTRAL EXCISE & SALES TAX:

➢ MM Consultant
➢ SD Consultant
➢ FI Consultant : Job creation of Accounts and Assignment of Accounts
➢ Central Excise is an Indirect Tax
➢ This will be levied at the time of Sales (Removal of goods)
➢ Central Excise Registration plant wise
➢ Central Excise registration – 15 digits (10 digits PAN + 5 digits Central Excise No)
➢ Central Excise rates are given in Central Excise Tariff
➢ In Central Excise Tariff we have chapter IDs – 8 digits code – Under chapter ID
material description and rate.

Excise duties are classified in to 3 categories :

a. Basic excise duty (BED) :Most of the products come under this category – now the
maximum rate is 10 % and the minimum rate is 5 %.
b. Special Excise duty: Tobacco related Products – 8 % on SED.
c. Additional Excise duty: Again limited products like textiles – 15 % on Base amount
– Now on AED.
d. Education CESS 2% and Higher Education CESS 1 % - Total 3%

1) CENVAT (Central Excise Value Added Tax) : (Earlier MODVAT):

When we pay Excise duty at the time of purchase, the Excise amount can be
adjusted when we pay excise duty on sales to excise department (Though collected from
customer).

2) RG 23A- Excise Duty on Consumables:

✓ We can claim 100 % in the same year.

✓ RG23A – Part I – Quantity Updation.
✓ RG23A – Part II – Value Updation
3) RG23C – Excise Duty on Capital goods:
✓ We have to claim 50 % this year, 50% next year.
✓ RG23C – Part I – Quantity Updation.
✓ RG23C – Part II – Value Updation.

94
SAP Real Time Content

4) Personal Ledger Account – Bank Excise credits & debits:

5) ER1 – Excise Return 1 – (Earlier it was RT12)- Monthly Return :
✓ To pay Excise before 5th of next month.
✓ To file return before 10th of next month.
6) RG1 –Finished goods registers.

PURCHASE SCENARIO :
Consumables Capital Goods
Purchase Purchase (Stores)
Basic Price 100 200
Excise 8 (8%) 20 (10%)
108 220
VAT – 4% 4.32 8.8
Total 112.32 228.8
Consumables Purchases:
a) In case of goods receipt – 2 entries will be passed.
1. Inventory RM a/c dr 100
To GR/IR Clearing a/c 100
2. RG23A a/c dr 8
To CENVAT Clearing a/c 8
b) Invoice Verification:
GR/IR Clearing a/c dr 100
CENVAT Clearing a/c dr 7
VAT Receivable a/c dr 4.32
To Party a/c 112.32
Capital Goods Purchases:
a) In case of goods receipt – 2 entries will be passed.
1. Inventory Stores a/c dr 200
To GR/IR Clearing a/c 200
2. RG23C a/c dr 10
CENVAT on Hold a/c dr 10
To CENVAT Clearing a/c 20
b) Invoice Verification:
GR/IR Clearing a/c dr 200
CENVAT Clearing a/c dr 20
VAT Receivable a/c dr 8.80
To Party a/c 228.80
95
SAP Real Time Content

SALES SCENARIO :
Basic Price 1000
Excise – 10% 100
1100
VAT – 14.5% 159.50
Total 1259.50
1. In case of Sales:
Customer a/c dr 1259.50
To Sales a/c 1000
To CENVAT suspense a/c 100
ToVAT Payable a/c 159.50
2. In case of Excise Invoice Creation:
CENVAT Suspense a/c dr 140
To Excise duty payable a/c 140
3. Adjustment of Excise payable against RG23A / RG23C and PLA:
Excise duty payable a/c dr 100
To RG23A a/c 8
To RG23C a/c 10
To PLA a/c 82
4. Sales Tax payment to department:
VAT payable a/c dr 159.50
To VAT receivable a/c 13.12
To Bank a/c 146.38
The standard system comes with two tax calculation procedures.
• TAXINN – Conditional Based
• TAXINJ – Formula Based.
Client 000 – We have both procedures –
For implementations SAP suggests to go for TAXINN.
MATERIAL MANAGEMENT:
1. Activate Country Version India for specific years:
SPRO-> Financial Accounting-> Financial Accounting global settings-> Tax on
sales & purchases->Basic settings->India ->Activate country version india for
specific fiscal years.
-> Select position button.
-> For Ind, for the year: 2999.
-> Select Activate check box.
-> Save.

96
SAP Real Time Content

2. Check and change settings for tax processing;

SPRO-> Financial Accounting -> Financial Accounting global settings-> Tax on
sales & purchases -> Basic settings -> Check and change settings for Tax
processing (OBCN).
➔ Select new entries button.
➔ Process : D1
➔ Description: A/P Excise basic.
➔ Tax Type: 2 Input Tax.
➔ Posting INDI : 2 Separate Line Item.
➔ Save.
➔ Process : D2
➔ Description: A/P CST.
➔ Tax Type: 2 Input Tax.
➔ Select Nondeductible check box.
➔ Posting INDI : 3 Distribute to relevant expense / Rev items.
➔ Save.
➔ Process : D3
➔ Description: A/P VAT.
➔ Tax Type: 2 Input Tax.
➔ Posting INDI : 2 Separate Line Item.
➔ Save.
➔ Process : D5
➔ Description: A/R CST.
➔ Tax Type: 1 Output Tax.
➔ Posting INDI : 2 Separate Line Item.
➔ Save.
➔ Process : D6
➔ Description: A/R VAT.
➔ Tax Type: 1 Output Tax.
➔ Posting INDI : 2 Separate Line Item.
➔ Save.
3. Define Condition Types:
SPRO-> Financial Accounting-> Financial Accounting global settings-> Tax on
sales & purchases -> Basic settings -> Check Calculation Procedure.
➔ Double click on Define Condition Types.
➔ Condition Type : DSL1-A/P Excise Basic.
➔ ACC SEQ : JTAX.
97
SAP Real Time Content

➔ Cond Class : D-Taxes.

➔ Cal Type : A- Percentage.
➔ Cond Category : D-Tax.
➔ Select Item Condition check box.
➔ Condition Type : DSL2-A/P CST.
➔ ACC SEQ : JST1.
➔ Cond Class : D-Taxes.
➔ Cal Type : A- Percentage.
➔ Cond Category : D-Tax.
➔ Select Item Condition check box.
➔ Condition Type : DSL3-A/P VAT.
➔ ACC SEQ : JST1.
➔ Cond Class : D-Taxes.
➔ Cal Type : A- Percentage.
➔ Cond Category : D-Tax.
➔ Select Item Condition check box.
4. Creation of Tax Procedure :
SPRO-> Financial Accounting -> Financial Accounting global settings-> Tax on
sales & purchases-> Basic settings -> Check calculation procedure.
➔ Double Click on define procedures.
➔ Select new entries button.
➔ TAX procedure – TAXINN – Sales Tax India.
➔ Save.
➔ Select : TAXINN
➔ Double Click on control data folder.
➔ Select new entries button.
ACC
ALT
STEP CTYPE DESCRIPTION FROM TO STAT PRINT T
CBV
KEY
100 BASB Base Amount 362
110 Calculated Cell 100 X
120 DSL1 A/P Excise BED 100 X D1
150 Basic + Excise 110 140 X
160 DSL2 A/P CST 150 X D2
170 DSL3 A/P VAT 150 X D3

98
SAP Real Time Content

5. Assign Country to Calculation Procedure:

SPRO-> Financial Accounting -> Financial Accounting global settings-> Tax on
sales & purchases -> Basic settings -> Assign country to calculation procedure.
➔ IN : TAXINN.
6. Creation of Tax codes (FTXP).
➔ V0 – 0% Input Tax.
➔ V1- Dummy Tax code for Input Tax
➔ A0- 0% Input Tax.
➔ A1- Dummy Tax code for Output Tax.
➔ Condition Type : DSL2-A/P CST.
➔ ACC SEQ : JST1.
➔ Cond Class : D-Taxes.
➔ Cal Type : A- Percentage.
➔ Cond Category : D-Tax.
➔ Select Item Condition check box.
7. Creation of GL Accounts-FS00
➔ 200156 – RG23A-Copy 200155 VAT Receivable.
➔ 200157 – RG23C- --Do--.
➔ 200158 – CENVAT on Hold –Do—
➔ 200159 – PLA Account –Do--.
➔ 200155 – VAT Receivable – Already Created.
➔ 100521 – CENVAT Clearing A/c – Copy 100505 VAT Payable.
➔ 100522 – CENVAT Suspense A/c –Do--.
➔ 100523 – Excise Duty Payable A/c – Created.
➔ 100505 – VAT Payable – Created.
➔ 100524 – CST Payable – Do--.
8. Assignment of Accounts for Automatic Postings:
SPRO-> Financial Accounting-> Financial Accounting global settings-> Tax on
sales & Purchases -> Posting -> Define Tax accounts (TC: OB40).
➔ Double Click on D1 – Chart of Accounts – DSL.
➔ Save
➔ Select Position button.
➔ Debit : 40
➔ Credit : 50
➔ Save in your request.
➔ Select Accounts button.

99
SAP Real Time Content

➔ 100521 – CENVAT Clearing

➔ Save
➔ Double click on D3.
➔ Select Posting key button.
➔ Debit : 40
➔ Credit : 50
➔ Save in your request
➔ Select Accounts button.
➔ For X3 : 200155 – VAT Receivable
➔ Save in your request.
➔ Double Click on D5
➔ Select Posting key button.
➔ Debit : 40
➔ Credit : 50
➔ Save in your request.
➔ Select Accounts Button.
➔ For X4 – 100524 – CST Payable.
➔ Save in your request.
➔ Double click on D6
➔ Select Posting key button.
➔ Debit : 40
➔ Credit :50
➔ Save in your request.
➔ Select Accounts button.
➔ For X4 : 100505 – VAT Payable.
➔ Save in your request.
9. Maintain Excise Registrations:
SPRO-> Logistics General-> Tax on goods Movement-> India-> Basic settings ->
Maintain Excise Registration.
Every factory that manufactures excisable goods is required to
register separately, so that a business with seven factories requires seven
registrations.
Excise REG ID : 150
ECC NO
Excise Reg, AAACG8605NXM005
Excise Range BALANAGAR
Excise Division HYDERABAD
Commissioner HYDERABAD
100
SAP Real Time Content

Duty Applicability:
• Deselect on liable AED
• Deselect on liable to CESS.
Options
Partial Credit – Tick.
No of Items in Excise Limit : 999
Save.
10. Maintain Company Code Settings:
SPRO-> Logistics General -> Tax on goods Movement-> India-> Basic Settings
-> Maintain Company Code Settings.
In this IMG activity, you maintain the data relating to your company
codes.
➔ Company Code : DSL
➔ CENVAT document type : SA
➔ Utilization FI Document type : SA
➔ Select Debit account override.
➔ Select Auto adjustment indicator.
➔ Select Immediate Credit on capital goods.
➔ Excise Invoice selection days : 30 (First Month of April)
➔ No of Excise Invoice Selection : 999
➔ EI Selection procedure : FIFO
➔ Save
11. Maintain Plant Settings:
SPRO-> Logistics General -> Tax on goods movement -> India -> Basic Settings
-> Maintain Plant settings.
➔ Plant : DSLP
➔ Excise Registration No : 150
➔ GRs per Excise Invoice : Multiple goods receipts, Multiple Credits.
➔ Save
12. Maintain Excise Groups:
SPRO-> Logistics General -> Tax on goods movement -> India -> Basic Settings ->
Maintain Plant settings.
➔ Excise Group : 30
➔ Plant : DSLP
➔ Description : Excise Group for DSL
➔ Excise Regn No : 150
101
SAP Real Time Content

➔ No.GRS per Excise Invoice : Multiple goods receipts, Multiple Credits.

➔ Select EI Capture
➔ Select Post Excise Invoice in MIGO
➔ Select duty different at GR
➔ Save.
Local Sales, Exports, Stock Transfer – All one Series.
13. Maintain Series Group:
SPRO-> Logistics General -> Tax on goods movement -> India -> Basic Settings
-> Maintain Series Group.
SERIES GROUP SERIES DUES EXC REG
30 Series Group for deccan steels ltd 150

14. Maintain Excise Indicators :

SPRO-> Logistics General -> Tax on goods movement -> India -> Basic Settings
-> Excise Duty Indicators.
EXC. IND +
1 100% Tax
2 50% Tax
3 Nil Duty

15. Maintain Excise Defaults:

SPRO-> Logistics General -> Tax on goods movement -> India -> Basic Settings
->Maintain Chapter ID’s.
Tax Proc CVD Exp Tax A/P A/P SED A/P AED A/R
Cond Code BED Cond Cond BED
Cond
TAXINN DSL1 DSLA

A/R SED A/R A/R BED % AED % SED % CESS %

AED CESS
DSL4

16. Maintain Chapter ID’s:

SPRO-> Logistics General -> Tax on goods movement -> India -> Basic Settings
-> Maintain Chapter ID’s.
72181000 INGOTS
72221111 STEEL BARS
-> Copy from Existing One.

102
SAP Real Time Content

17. Maintain Special GL Accounts for Excise Transactions:

SPRO-> Logistics General -> Tax on goods movement -> India -> Basic Settings
->Special GL Accounts Per Excise Transactions.
➔ Select New Entries button.
➔ Excise Group : 25/30.
➔ Excise Transaction Type : GRPO (Excise Invoice for goods receipt against PO).
➔ Company Code : DSL.
➔ Chart of Accounts : DSL.
➔ RG23A BED : 200156.
➔ RG23A BED : 200157.
➔ MODVAT Clearing : 100521.
➔ G/L Account for PLA BED : 200159.
➔ CENVAT on Hold : 200158
➔ CENVAT SSE ( Suspense A/c) : 100522.
➔ PLA on Hold : 200159
➔ Save.
➔ Press enter to save in your request.
➔ Select the item what we have created.
➔ Copy for all excise transactions types.
➔ Select Extransaction types : DLFC.
➔ Change RG23ABED : 100523.
➔ RG23CBED : 100523
➔ Save.
18. Assign Billing Types to Delivery Types :
SPRO-> Logistics General -> Tax on goods movement -> India ->Business
Transactions-> Out going Excise Invoice -> Assign Billing types to delivery types.
DII Type Billing Type
LF F2
NL JEX

19. Specify SAP Script Forms:

SPRO-> Logistics General -> Tax on goods movement -> India ->Business
Transactions->Excise Registers-> Specify SAP Scripts forms.
➔ Select All Forms For IN01.
➔ Copy To Company Code : DSL.

103
SAP Real Time Content

20. Number Ranges :

SPRO-> Logistics General -> Tax on goods movement -> India ->Business
Transactions-> Tools-> Number Ranges.
➔ Object Long Text.
➔ J_1IINTNUM – Internally document No. to be generated.
➔ Select Number Ranges button.
➔ Select Intervals button.
➔ Select Interval button.
➔ No Range : 10
➔ Year : 2011
➔ From Number : 1
➔ To Number : 100000
➔ Save – Ignore the warning message and press enter.
➔ Select back arrow 2 times.
➔ J_1IRG23A1-RG23A Part- I Updation0
➔ Select Number Ranges button.
➔ Excise Group : 30/25
➔ Select Intervals button.
➔ Select Interval button.
➔ No Range : 01
➔ Year : 2011
➔ From Number : 100001
➔ To Number : 200000
➔ Save – Ignore the warning message and press enter.
➔ Select back arrow 2 times.
➔ J_1IRG23A2- RG23A Part-II Updation.
➔ Select Number Ranges button.
➔ Excise Group : 30/25
➔ Select Change intervals button.
➔ Select Interval Button.
➔ No Range : 01
➔ Year : 2011
➔ From Number : 200001
➔ To Number : 300000
➔ Save – Ignore the warning message and press enter.
104
SAP Real Time Content

➔ For Sales :
➔ J_1IEXCLOC- Local Excise Invoice No Range.
➔ Select Number ranges button.
➔ Series Group : 30
➔ Select Change Intervals button.
➔ Select Interval button.
➔ No Range : 01
➔ Year : 2011
➔ From Number : 300001
➔ To Number : 400000
➔ Save – Ignore the warning message and press enter.
➔ J_1IINTPR2-Despatch serial number.
➔ Select Number ranges button.
➔ Excise group : 30
➔ Select change intervals button.
➔ Select Interval button.
➔ No Range : 01
➔ Year : 2011
➔ From Number : 400001
➔ To Number : 500000
➔ Save – Ignore the warning message press enter.
21. Excise Rate Maintenance :
➔ Use Transaction Code : J1ID
➔ Indirect Taxes -> Master Data -> Excise Rate Maintenance.
➔ Transaction Code : J1ID.
➔ Select Material and chapter ID Combination.
➔ Select details button.
➔ Select New entries button.
➔ Material : DSLRM1
➔ Plant : DSLP
➔ Chapter ID : 72181000
➔ Material Type : RAW MATERIAL.
➔ GR X Ref : Multiple goods receipts, Multiple Credits.
➔ Declared : X
➔ Declaration date : 28.02.2011.
➔ Select new entries button
105
SAP Real Time Content

➔ Material : DSLFG
➔ Plant : DSLP
➔ Chapter ID : 72221111
➔ Material Type: Finished Goods.
➔ GR X Ref: Multiple goods receipts, Multiple Credits.
➔ Declared: X.
➔ Declaration date : 28.02.2011
➔ Save.
➔ Select back arrow.
➔ Select CENVAT determination radio button
➔ Plant : DSLP
➔ Input Material : DSLRM1
➔ Output Material: DSLFG.
➔ Intimation date : 28.02.2010
➔ Save
➔ Select back arrow.
➔ Select Vendor Excise details radio button.
➔ Select Maintain button.
➔ Vendor No 2000301 – DSL MM VENDOR.
➔ Excise Indicator for Vendor: 1 Liable For Tax.
➔ Type of Vendor: Manufacturer.
➔ Save.
➔ Select back arrow.
➔ Select Customer Excise details radio button.
➔ Select Maintain button.
➔ Customer No 3000301- DSL SD CUSTOMERS.
➔ Excise Indicator for customer: 1Liable for Tax.
➔ Save.
➔ Select back arrow.
➔ Select Excise indicator for plant radio button.
➔ Select Maintain button.
➔ Select New entries button.
➔ Company Code : DSL
➔ Plant : DSLP
➔ First Month : April
➔ Excise Indicator for Company : 1 Liable for Tax.
106
SAP Real Time Content

➔ Save
➔ Select back arrow.
➔ Select Excise Indicator for plant and vendor radio button.
➔ Select Maintain button.
➔ Select New Entries.
➔ Excise Indicator for Company : 1
➔ Excise Indicator for Vendor : 1
➔ Excise Indicator : 1
➔ Save.
➔ Select back arrow.
➔ Select Excise indicator for plant and customer radio button.
➔ Select maintain button
➔ Select new entries button.
➔ Excise Indicator for Company : 1
➔ Excise Indicator for Customer : 1
➔ Excise Indicator : 1
➔ Save
22. Condition Record for Excise Duties :
The Purpose of the activity is to create condition records for excise
duties in the purchase order.

Procedure:
1. Access the activity using one of the following navigation options :
Transaction Code : FV11.
2. Condition Type : Select DSL1- Select Key Combination button.
3. Choose the Plant / Vendor / Material Combination and Choose Enter :
FIELD NAME DESCRIPTION DEFAULT VALUES
Plant DSLP
Vendor 2000301
Material DSLRM1
Amount 8
Tax Code V0
23. Creating Condition Record for sales Tax Condition Type :
Procedure:
1. Access the activity using one of the following navigation options :
Transaction Code : FV11.
2. Condition Type : Select DSL3 - Select Key Combination button.

107
SAP Real Time Content

3. Choose the Plant / Vendor / Material Combination and Choose Enter :

Choose Enter
The Following Key Fields were used :
FIELD NAME DESCRIPTION DEFAULT VALUES
Plant DSLP
Vendor 2000301
Material DSLRM1
Amount 4
Tax Code V0

Save.

1. Creation of Purchase Order :

SPRO-> Logistics -> Materials Management-> Purchasing-> Purchase Order ->
Create -> Vendor / Supplying Plant Known (TC: ME21N)
➔ Vendor No : 2000301.
➔ Purchasing Organization : DSLR.
➔ Purchasing Group : DSL
➔ Company Code : DSL.
➔ Item : 10
➔ Material : DSLRM1
➔ PO Quantity : 1000 Kgs.
➔ Net Price : 100 Rs.
➔ Currency : INR.
➔ Plant : DSLP.
➔ Select Invoice Tab : Select Tax Code : Change Tax Code to V1- Dummy Tax
Code for Purchases.
➔ Select Taxes button.
➔ Select Back arrow.
➔ Save.
2. Goods Receipt :
SPRO -> Materials Management -> Inventory Management -> Goods Movement
-> Goods Movement (TC: MIGO).
➔ Select Goods Receipt.
➔ Purchase Order No : 4500017093
➔ Enter.
➔ Select Where Tab.
➔ Storage Location : HYD.
108
SAP Real Time Content

➔ Select Quantity Tab.

➔ Quantity in Delivery Note : 1000 Kgs.
➔ Select Item OK Check Box.
➔ Enter.
➔ Select Excise Item Tab.
➔ To see the Excise Values.
➔ Also Select Excise Invoice Tab.
➔ Excise Invoice No : 1
➔ Excise Invoice Date : Today’s Date.
➔ Select Check button.
➔ Post
➔ 2 Documents will be generated.
➔ One for GR and another for Excise: Debit RG23A and Credit to CENVAT
Clearing A/c.
➔ Select Display
➔ Enter.
➔ Select Document Information Tab.
➔ Select FI documents button.
➔ Select Excise Invoice.
➔ Select More data button.
➔ Select Part 2 Tab.
➔ Select Accounting Document No.
3. Invoice Verification :
SPRO -> Logistics -> Material Management -> Logistics Invoice Verification ->
Document Entry (TC: MIRO).
➔ Invoice Date : Today’s Date.
➔ Reference : 1234.
➔ Select The Tax Code : V0
➔ Give Purchase No : 4500017093
➔ Enter.
➔ Amount : 1,12,320
➔ Save.
4. Extract Excise Registers :
➔ Use TC : J1ILN
➔ Indirect Taxes -> Registers -> Excise Tax-> Extract (J215)
➔ Select RG23A Part-I (Qty)

109
SAP Real Time Content

➔ Select RG23A Part – II (Value)

➔ Excise Group : 30/25
➔ Start date : 01.06.2011
➔ End date : 30.06.2011
➔ Execute
➔ Select Back arrow.
➔ Excise Tax -> Print Utility Program (J2I6)
➔ Print Register:
➔ Select RG23A Part-I (Qty Information)
➔ Execute
➔ Excise Group : 30
➔ Start Date : 01.06.2011
➔ End date : 30.06.2011
➔ Out put Device : LP01
➔ Select Print Preview button.
➔ Select Back arrow.
➔ Select RG23A Part – II (Value Information)
➔ Execute
➔ Excise Group : 30
➔ Start date : 01.06.2011
➔ End date : 30.06.2011
➔ Output Device : LP01
➔ Select Print Preview button
➔ Select Back arrow.
5. To View Sales Tax Register:
➔ Up to Registers the Path is same-> Select Sales Tax Folder-> Sales Tax Register
(TC: J1I2).
➔ Company Code : DSL
➔ LST Condition Type : DSL3
➔ Select Execute button.
SALES AND DISTRIBUTION
1. Creation of Condition Type :
SPRO->Sales and Distribution -> Basic Functions -> Pricing -> Pricing Control
-> Define Condition Types.
➔ Double Click on Maintain condition types.
➔ Select New entries button.

110
SAP Real Time Content

➔ Condition Type : DSL4 (A/R BED %)

➔ Access SEQ : JEXC (India Excise).
➔ Condition Class : A
➔ Plus / Minus – A Position.
➔ Calculation Type : A
➔ Select Amount / Percent Check Box.
➔ Select Item Con Check Box.
➔ Save.
➔ Condition Type : DSLA (A/R BED ) 100% Copy.
➔ Access SEQ : JDUM (India Excise).
➔ Condition class : A
➔ Plus / Minus – A Position.
➔ Calculation Type : A
➔ Select Amount / Percent Check Box.
➔ Select Item Con Check Box.
➔ Save.
➔ Condition Type : DSL5 (A/R CST)
➔ Access SEQ (Central Sales Tax)
➔ Condition Class : D Taxes
➔ Plus / Minus – Blank
➔ Calculation Type : A Percentage
➔ Condition Category : D Taxes.
➔ Select Amount / Percent Check box.
➔ Select Item Con Check box.
➔ Save.
➔ Condition Type : DSL6 (A/R LST)
➔ Access SEQ : JLST (Local Sales Tax)
➔ Condition Class : D Taxes
➔ Plus / Minus : Blank
➔ Calculation Type : A Percentage
➔ Condition category : D Taxes
➔ Select Amount / Percent Check box
➔ Select Item Con Check box
➔ Save.
2. Define Account Keys :

111
SAP Real Time Content

SPRO-> Sales and Distribution-> Basic Functions -> Account Assignment/

Costing -> Revenue Account determination -> Define and Assign account keys.
➔ Double Click on Define Account Key.
➔ Select New Entries button
➔ D4 – Excise Duty
➔ D5 – A/R CST.
➔ D6 – A/R VAT
➔ Save.
3. Creation Pricing Procedure (V/08)
SPRO-> Sales and Distribution-> Basic functions -> Pricing Control -> Define
and Assign Pricing Procedures.
➔ Double Click on Maintain Pricing Procedures.
➔ Procedure : DSL – Domestic Billing.
➔ Select New Entries button.
Step Cond Description From To Re Stat Print Account
No Type Step Step q Key
100 PR00 Price X X ERL
105 Calculated Cell 100 100
110 DSL4 A/R BED % 100 100 X D4
120 DSLA A/R BED 100% 110 110 X
Copy
150 Calculated Value 105 105 X
160 Basic + Excise 120 150 X
170 DSL5 A/R CST 160 160 D5
180 DSL6 A/R LST 160 160 D6
200 Base + ED + ST 160 180 X

110 – For Percentage Calculation Procedure – DSL4

120 – For Totaling Purpose 120 to 150 – DSLA
4. Define Pricing Procedure Determination :
SPRO-> Sales and Distribution -> Basic Functions -> Pricing -> Pricing Control
-> Define and Assign Pricing Procedures.
➔ Double Click on Define Pricing Procedure Determination.
➔ Select Position button.
➔ Give Sales Organization – DSLS
➔ Press Enter.
➔ Pricing Procedure – DSL
➔ Save
5. Define Tax Determination Rules :
➔ Tax Determination in Master Records
112
SAP Real Time Content

➔ Define Tax Determination Rules

➔ SPRO -> Sales and Distribution-> Basic Functions-> Taxes-> Define Tax
Determination Rules.
IN INDIA 1 DSL5 A/R CST
IN INDIA 2 DSL6 A/R VAT

6. Define Tax Relevancy of Master Records:

SPRO-> Sales and Distribution -> Basic Functions -> Taxes -> Define Tax
Relevancy of Master Records.
➔ Customer Taxes (TC: OVK3)
TAX CATEGORY TAX CLASSFICATION DESCRIPTION
DSL5 0 NIL TAX
DSL5 1 TAXABLE
DSL6 0 NIL TAX
DSL6 1 TAXABLE
➔ Material Taxes (TC:OVK4)
TAX CATEGORY TAX CLASSFICATION DESCRIPTION
DSL5 0 NIL TAX
DSL5 1 TAXABLE
DSL6 0 NIL TAX
DSL6 1 TAXABLE
7. Assign Delivering Plants for Tax Determination:
SPRO-> Sales and Distribution -> Basic Functions-> Taxes -> Assign Delivering
Plants for Tax Determination (TC: OX10).
➔ Assign for Plant : DSLP
➔ Region : AP (Mandatory)
8. Assignment of Accounts for Automatic Posting (TC: VKOA):
SPRO-> Sales and distribution -> Basic function-> Account Assignment/ Costing
-> Revenue Account Determination -> Assign GL Accounts.
APP COND CA SALES AA AAG ACCT GL
TYPE ORG KEY
V KOFI DSL DSLS 01 03 D4 100522
100522 – CENVAT Suspense A/c
9. Assign Tax Classification in Customer Master (TC: XD02):
➔ Select Sales Area data button.
➔ Select billing documents tab.
TAX CATEGORY TAX CLASSIFICATION
DSL5 BLANK
DSL6 1- TAXABLE

113
SAP Real Time Content

10. In Material Master enter Tax Classification (TC: MM02)

➔ Material : DSLFG
➔ Press Enter
➔ Select Views Button
➔ Select Sales : Sales Org
➔ Enter
➔ Plant : DSLP
➔ Sales Org : DSLS
➔ Distribution Channel : DD
➔ Enter
TAX CATEGORY TAX CLASSIFICATION
DSL5 1- TAXABLE
DSL6 1- TAXABLE
11. Creation of Condition Records (TC : VK11)
➔ Select DSL4 – A/R Excise
➔ Select Key Combination button
➔ Select 004 Material
➔ Sales Organization : DSLS HYD Sales Organization
➔ Distribution Channel : DD Direct Sale
➔ Material DSLFG 10% 01.04.2011 31.12.9999
➔ Save
➔ For DSLA-A/R Excise 100% Copy
➔ Select Key Combinations
➔ Select Sales Organization
➔ DSLS Sales Org HYD 100% 01.04.2011 31.12.9999
➔ For DSL6 – A/R VAT
➔ Select Country / Plant / Region / Material
➔ Country : IN India
➔ Plant : DSLP
➔ Region : AP Andhra Pradesh
➔ Material DSLFG 14.5% 01.04.2011 31.12.9999 A1 (Dummy Code For
Sales )
12. Creation of Sales Order (VA01)
13. Delivery with PGI (VL01N)
14. Billing (VF01)
15. Local Excise Invoice Creation Go To J1ILN
114
SAP Real Time Content

➔ Select Indirect Taxes -> Sales -> Outbound Movements-> Excise Invoice->
For Sales order-> Outgoing Excise Invoice (J1IIN)
➔ Select From billing
➔ Billing Document :
➔ Enter
➔ Excise Group : 30
➔ Series Group : 30
➔ Select Utilization (Calculator) Button
➔ By defaults excise Invoice Type local will come
➔ Save
16. Excise Utilization:
➔ Use the TC: J1ILN
➔ Indirect Taxes -> Sales -> Outbound Movements-> Fortnightly Payment
(J2IUN)
➔ Company Code : DSL
➔ Plant : DSLP
➔ Excise Group : 30
➔ Period : 01.06.2011 to 30.06.2011
➔ Select execute button.

115
SAP Real Time Content

IMPORTANT INTERVIEW QUESTIONS :

1. What is the purpose of group a/c number
2. Where we have to define the group a/c number
3. What is the purpose of keyword translation tab
4. What is the prerequisite to make the GL master as a clearing ac
5. What is the purpose of sort key, is that mandatory
6. What is the purpose of the reconciliation ac and can we change in the middle of the
year
7. What is the planning level
8. What is the purpose info COA
9. what is company code and what are the assignments will be made to company code
10.In which table vendor ac group will be saved
11.Where the payment method for customer will be assigned
12.What are the available radio buttons for payment terms
13.What is the purpose of tolerance group for employees
14.What is mm flow and entries
15.How the mm flow entries will be generated
16.Valuation area and GL account
17.What is valuation modifier
18.What are customer master tables
19.What is the app customization, how do u clear foreign vendor using app, how the
bank determination influences the foreign vendor
20.What are the steps in BRS
21.For cheque issue ac what will be entry & how the posting rule created & how it is
updated
22.Give an example for which GL ac post automatically check box should be selected
23.If we forget to select Open Items for cheque issue ac how the main bank ac reflect
24.Give me the steps in assets accounting
25.I want to activate book depreciation as required entry field what is the process to do
that
26.What is the purpose of ordinary depreciation
27.What is the purpose of unplanned depreciation run and where can we see that
28.What is validation and substitutions tables, & process & purpose
29.What is asset sale entry & reverse of asset sale entry
116
SAP Real Time Content

30.Depreciation posting entry

31.Wheather f-53 and app is having same document type or not, if client required
separate document type what we have to do
32.What are the data migration type
33.What are the Lsmw steps
34.How the transaction data will be transferred
35.How many cost centers do u maintain
36.What is document splitting and what is the purpose of document splitting
37.Why sap suggest segments rather than business area and how they resolve problem
38.Where does vendor bank details will be stored
39.What is the purpose of creating cost element
40.What is the tool you are using
41.Do u have any idea regarding solution manager
42.What is system development life cycle
43.From which phase ur involved
44.What is ur role in final preparation
45.What is ur go live date

117