Quantcast
Channel: SCN : Document List - SAP ERP Financials
Viewing all 366 articles
Browse latest View live

Excise Duty Process Flow

$
0
0

Excise Duty Process Flow

TR6 Challan Creation

General Ledger Document Creation (FB50)

 

System does not update the PLA Register with the above entry. When you update the TR6 Challan updating process, the system will update the PLA Register and PLA Account and reverse the PLA on Hold Account.

 

Invoice to Tax Authority (FB60/F-43)

 

In this activity, you debit the PLA Interim Clearing Account so that the same is nullified and credit the Tax Authority for the payment of PLA.

 

Payment to Tax Authority (F-58)

In this activity, the Cheque has been issued to the Tax Authorities/Bank.

 

TR6 Challan Posting

 

Transaction Code  J1IH

On Excise JV Main Menu, select the TR6 Challan Tab. Once you click on the TR6 Challan.

You have to enter the GL Document created in the 1st step, Document Year, Company Code, Plant and Excise Group for which the PLA Payment is being made.

Press “Enter”.


 

You can observe that the PLA on Hold Account is getting credited which was 1st debited in the GL Account Document creation.Enter the PLA BED, PLA EduCess & PLA SHECess amounts to debit the same

 

After filling the required amounts post the document. Once you save the document, the following line will appear at the bottom of the sap screen


You can view the same by clicking on the –> Main Menu –> Excise JV –> Display and fill the following

 

 

Click on the Accounting Document Tab:

The Result of the above document is: The PLA on Hold Account has been nullified & PLA BED, PLA EduCess & PLA SHECess has been debited.

 

Cenvat Utilization

 

                       

Process Overview

The trigger for this transaction is the requirement of CENVAT Utilization. It is used to calculate

how much Excise Duty you must remit to the authorities. Legislation requires you to remit

excise duty monthly. Companies are allowed 5 days to remit excise duty except for the Month of March

 

Once the report has determined how much you have to pay, it allows you to specify where

money should be paid from i.e. whether it should be deducted from the CENVAT credits that

you have accumulated in RG23A Register or RG23C Register, or whether it should be deducted

from the Personal Ledger Account (PLA). You have the option of selecting the appropriation

amounts as required.

 

 

Prerequisites: User must be assigned to the Country India Specific Menu i.e. J1ILN. Excise

Invoices must be posted in the System to arrive the CENVAT Payable for deliveries made from

the Factory. The CENVAT Payable amount should be credited to a Clearing Account as a

  1. Liability. At the time of Utilization of CENVAT, the system will post the Debit entry to the

same account based on the Account assignments in the Customization.

 

 

 

 

 

 

 

 

  • Utilization of CENVAT (J2IUN)

In the above screen, you have to input the following: Sub Transaction Type

ADC Sub Transaction Type

 

Excise Invoice Selection

Period: It is the period of all the Excise Invoices for which you are running a Utilization Entry.

Excise Invoice: You can restrict the selection of Invoices here by selecting them in Exclude Single Invoice or Invoice Range.

 

 

 

 

Business Area: This is below the Plant Level. Note: There is no multiple Business Area selection in this field & the filling of Business Area is compulsory otherwise the GL Entry is not possible.

Display Last Utilization Date Tab: It shows you when the last Utilization was made. The next utilization can be done only if you put a date which is next to the last Utilized Date.

Display Pending Invoices: It shows the pending invoice to be selected in this Utilization Run.(Including the Invoices given in the Excise Invoice Selection Restriction Field - Excise Invoice)

Once you have input all the Necessary Fields, you will see the following screen:


Now select the Duty which you want to adjust against the available credit, and select on select duty view button, you can view the concerned Duty Credit Available in related Excise Registers as well asthe Amount available in PLA for the same will appear as shown below:

 

In the above, screen the Registers Balance in RG23A BED is available so you can utilize it for thepayment of Excise Duty otherwise you have to use the balance available in PLA Register also.Youhave to utilize it as follows:

 

 

After selecting the ECS Duty, click on the “” button to view the concerned

Balances Availability, the following screen appears:

 

Enter the Duty as applicable.

 

 

After selecting the ECS Duty, click on the “” button to view the concernedBalances Availability, the following screen appears:

 

 

 

 


Click onthe following screen appears where you can check the accuracy of the Accounts and then post the same.



Once you save the above entry, the following message appears at the bottom of the SAP Screen.

 

You can view the Accounting Document through FB03.


 

In the above document, one can observe that the CENVAT Credit/Availed Accounts have been

credited and the CENVAT Payable Accounts have been debited.

 

 

 

 

 

 

 

 

























Creation of screen variant for SAP FI enjoy transactions in ECC 6.0 EHP 5 and above

$
0
0

Purpose


With the upgrade of ECC6.0 with EHP5, SAP has discontinued the option to change the layout of the enjoy transactions (FB50, FB60, FB65, FB70 and FB75) at end user level through screen variant. It was available in previous version.

 

The purpose of this document is to describe the process to create a layout for transaction FB60 through transaction variant creation.

 

Fig. FB60 Screen in ECC 6.0 EHP5

 

A.jpg

As you can see the 'Configuration' button is no more available for user to access. Now we need to create the layout for user through transaction SHD0 - Transaction variant.

 

Creation of screen variant


To create the new layout as per the user requirement, we need to create a screen variant. Execute the transaction SHD0 and Got to tab Screen variant.

B.jpg

Enter transaction code ‘FB60’, screen variant name, program name and screen number.

 

Here we want to change the layout (manage the columns) of the transaction FB60 - GL line items. So we have selected program ‘SAPLFSKB’ and screen ‘100’.

 

Now click on create button.

 

Here we are arranging the columns as per our requirement. One can arrange the columns by drag and drop functionality.


Note: By default there are 5 columns which are fixed in SAP program SAPLFSKB. To move the fixed columns (if required) we need to get ‘Access key’ for program SAPLFSKB and change the number of fixed column in transaction SE51. This task is to be performed by an ABAPer.


C.jpg

 

Once we done with arranging columns as per user requirement, press enter to continue. System may ask you to enter the vendor and document date details to proceed further.


System will give a new pop up screen.


D.jpg

 

PLease make sure you have selected check boxes for ‘Adopt Column Sequence’ and ‘Adopt Column Width’. Give the logical name and description of the variant and click on Continue.

E.jpg

Check all your settings, and click on save button.

 

Creation of user group

 

As we are done with the creation of screen variant, Now we need to assign this screen variant to a specific user. Before that we need to create user group. We create the user group so that same variant can be assigned to multiple users.

 

Go to tab Standard variants

 

F.jpg

First we need to create a user group. Enter the group name and click on create button. Make sure this user group name should start with letter ‘Z’.

 

G.jpg

Click on create.

H.jpg

Enter the group name and short text of the group and click on save button.

 

I.jpg

 

Here you can see that system has generated name for transaction variant ‘ZBR01_1FB60’.

 

We have to create the transaction variant with this key name so as to assign the screen variant to the user group.

 

Creation of transaction variant


Go to tab transaction variant

 

System automatically populates the transaction variant name in this screen.

J.jpg

Click on Display/Change button highlighted above. This will enable the options to assign screen variants to transaction variant.

 

K.jpg

 

Click on Insert row button.

Enter the screen variant created in the first step and press enter.

L.jpg

 

M.jpg

Click on save.

 

Assign user to user group

 

Go to Standard variant tab


N.jpg

O.jpg

 

Enter the username and click on ‘Assign’ button.

 

This assignment will assign the user to user group. The next step is to click on ‘Set Proposal’. With this step the screen variant actually becomes effective for user ID.

 

Now whenever this user execute the transaction FB60, he will see the screen as we defined in the screen variant ZBR01_1.

 

Similar to this you can create the screen variant for other enjoy transactions of SAP FI.

Difference between "display line items" flag marked and not marked (Entry view and GL view)

$
0
0

Hi Colleagues,

 

I created two scenarios below with line item display flag and without this flag to explain this function. But first, you've to understand the difference in the entry view and GL view.

 

The entry view is where you can see documents in the subledgers AP and AR. The GL view is where you can see these documents independent of subledgers. Always will be displayed by GL.

 

When a GL account is created, you've the option to mark the "Dislpay line items" checkbox. Technically, if the flag is marked, these line items will be copied to subledgers or entry view. If does not has the flag, e.g BSIK or BSAK (opened line items and cleared line items tables for vendor) won't displayed this line items and FBL3N or FAGLL03 in the entry view can't be displayed. BSIK and BSAK tables for vendor side, this can be applied for customer o GL side.

 

FBL3N has only entry view. FAGLL03 has two types of views: entry view and GL view. FAGLB03, FS10 and FS10N are displayed the balance independent of the flag. But to display line items by FS10 and FS10N. i.e, transactions that are used with entry view will be checked in the master data GL account if the flag is marked or not. If does not marked, line item won't appears.


In the FAGLL03 tcode when GL view is selected is independent of flag in the data master GL account because this transaction research BSEG table to find line items. This happens too with FAGLB03 to dislplay line item because this transaction use only GL view.

 

Check the screenshots below:

 

Without flag GL account 2010000000 and with entry view:


SKB1_line_item_display_1.jpg

FAGLL03

 

ScreenHunter_002.jpg

 

FBL3N

 

ScreenHunter_003.jpg

 

Without flag GL account 2010000000 and with GL view:


ScreenHunter_001.jpg

 

With flag GL account 2010001000 and entry view:

 

FBL3N

ScreenHunter_004.jpg

 

FAGLL03

 

ScreenHunter_005.jpg

 

If you created a GL account without this flag and after some time you want to activate it, you've to run RFSEPA01 program or FAGL_ACTIVATE_IT tcode. This transaction will copy the line items from BSEG table to BSIK and BSAK tables for vendor side. But, also can be applied for customer or GL side.

 

But before to run or activate this flag, read the program documentation.

 

 

JPA

Validation in Postal Code in Vendor / Customer Master

$
0
0

                Postal code is a unique data more helpful to track any address.     But in customer / vendor Master data often either  user skips this fields or fill something irrelevant if it supposed to be mandatory.     To create a validation rule for postal code I suggest a simple solution which an ABAPER can do without much effort.

 

 

                The first 2 digit of the postal code represents the State as given below :

 

 

  First 2
  Digits of PIN

  Circle

  11

  Delhi 

  12 and 13

  Haryana

  14 to 16

  Punjab

  17

  Himachal Pradesh

  18 to 19

  Jammu & Kashmir

  20 to 28

  Uttar Pradesh and Uttaranchal

  30 to 34

  Rajasthan

  36 to 39

  Gujarat

  40 to 44

  Maharashtra

  45 to 49

  Madhya Pradesh and Chattisgarh

  50 to 53

  Andhra Pradesh

  56 to 59

  Karnataka

  60 to 64

  Tamil Nadu

  67 to 69

  Kerala

  70 to 74

  West Bengal

  75 to 77

  Orissa

  78

  Assam

  79

  North Eastern

  80 to 85

  Bihar and Jharkand

  90 to 99

  Army Postal Service (APS)

 

Except 90- 99  all the ranges are possible values in postal code.    The “ Region”  field is used to capture the State.    The Pincode already entered by user can be verified by the Region selected by the user . 
For example  

 

 

First 2 digit of Pincode 60,61,62,63,64  are possible values for Region = 22  ( ie. Tamilnadu )

 

 

This simple validation will be more useful even though not cent percent accuracy to some extent validate the data entered.  

 

 

I invite all to improve the validation further towards more accuracy.

 

 

 

Selvakumar.N

Implementing Notes from Finance Customer Connection

$
0
0

After attending the News for FICO Friends: ERP for Financials Customer Connection webcast, we took a look at some of the notes and applied them.  As of now, some of the notes look very promising.  See below.

 

Display FI Document - Seeing more of the Name

Who entered that document?  Perhaps you don't know all the user names in your system.  That is what is nice about this enhancement.

1doubleclickname.jpg

 

The above is from the header document.  Double click on "Entered by" "TPOWLAS" and the following appears after implementing the note:

2seename.jpg

 

You can see the person's first name, last name, department and phone.

 

Opening and Closing Periods

How many of us know the account type codes?  I confess, I don't know all of them.  How many times has it caused us mistakes?

 

See old OB52:

3aoldob52.jpg

What is account type V?  I can't tell you right now without looking it up.

 

After implementing the notes from the Customer Connect, see below:

3newob52.jpg

 

Account type V is contract accounts and now the view above is nice to read and such a view should help prevent mistakes in the future.

 

Increasing Line Counts in CO Line Items

5aold.jpg

 

In KOB1 (CO Line items report) there is a line item limit.  Implementing the notes from the customer connect, this can be increased using transaction RPC0 transaction:

5rpc0increase.jpg

 

We are still investigating some of the other notes resulting from the Customer Connection - to be continued.  So far the notes have some great appealing features.

Foreign currency valuation F.05

$
0
0

This Document shows how execution of F.05 affect documents posted(unrealised part ) in foreign currency  and documents whose payments(realised part) in foreign currency   are carried out

 

 

1 Valuation Adj Account GL 93599 is where realized foreign ex gail  / loss will be posted

Tcode OBA1

10.png

 

2 Take screenshot of Ex rate maintained in Tcode OB08

 

3 Posting of document and display

FB60 & FB03

11.png

 

4 Execution of F.05 and display of document  posted ( This is posting of unrealized part ie no payment done yet )

12.png

5 Posting payment and disply of document

F-53 & FB03

13.png

6 Now will recheck Document posted in 3 above

FB03

14.png

This is realized Gain /loss on foreign exchange & will be part of profit & loss accounts and no entries will get reversed here .

 

 

I am open for more question .

 

Regards

kaushal

Usage of Worklist Functionality in Asset Accounting-Part I

$
0
0
  1. Introduction to Worklist Functionality in SAP


On numerous instances an entity might want to carry out mass retirements, mass transfers or mass changes to asset master data. For example, an organization might dispose a major portion of its Fixed Account and might have to account for the retirement of the same in its books.


This document explains the usage of worklist functionality in asset accounting. This functionality enables the us to carry out mass transactions like retirement, transfers etc. without having to develop an LSMW for the same. The worklist functionality can be used to:

 

  • Carrying out mass retirement of asset without revenue or with revenue.
  • Mass inter-company asset transfer.
  • Making mass changes to asset master data


The usage of worklist functionality for each of these instances is explained subsequently. Basically this functionality would involve two steps:

a) Grouping assets for which similar processing has to be done-this is achieved by creation of worklist. b) Releasing the worklist so created which would complete the processing on the assets(i.e. transfer, changes or retirement).


This document would describe the usage of worklist functionality to carry out mass retirement with revenue and without revenue and mass intercompany asset transfer The other instances i.e. mass changes to asset master involves some additional steps and are described in Part II of the document.

  

2.1  Retirement of Assets (without Revenue)


The retirement of assets can be carried out using the transaction code ABAVN. However when an entity desires to retire more than one asset
at a time it can use the worklist functionality to post the mass retirement of assets. This will enable the entity to post the retirement of all assets at a time.

 

For creation of worklist, following is the path:

Easy Access Path:
Accounting - Financial accounting - Fixed assets - Environment - Worklist –Generate. (T-code is AR01)

 

At this stage we enter the company code, asset number and asset sub number of the assets which have to be retired. There is possibility of giving additional selection options like asset class, cost center, plant also as given in the screenshot below:

pic1.png 


Thereafter we proceed to create the Worklist by clicking on the ‘Worklist’ tab in the following screen that appears on execution:


pic1.png

We give the name of the worklist (any task- name to be input by the user) and the retirement option (in this case Retirement without
revenue)

pic4.png


In addition, we enter various other parameters like the posting date, document date, asset value date and transaction type for posting the mass retirement. The text that has to be populated during the retirement also has to be entered.


pic1.png

On doing so a work queue gets added. All the selected assets which we need to be retired get added to this work queue.

pic3.png

 

The next step is to release the worklist. The easy access path for the same is Accounting - Financial accounting - Fixed assets -
Environment - Worklist – Edit (T-code for the same is AR31)

 

In the screen that appears, we give the work queue number and execute the same. Then we release the work queue as shown below:

pic5.png

  Once released, the following screen appears:

pic6.png

Check the error log for errors if any:

The entry that gets passed is given below. The accumulated depreciation account is debited and the corresponding asset account is
credited. The text given at the time of creation of worklist gets populated here as shown below:

pic8.png

 

2.2  Retirement of Assets (with Revenue)


The retirement of assets with revenue is similar to the retirement of assets without revenue except for the accounting treatment that has to be followed in case of the resultant revenue derived from the sale of asset and the proportion of distribution of the same to the various assets.


The assets that have to be retired are added to a worklist by using transaction AR01:

pic9.png


pic10.png

 

An additional step that has to be followed in case of retirement with revenue is to determine the sale proceeds that will be realized from the assets and the proportion in which the same will be distributed amongst various assets.


The manner of distribution of sale proceeds can be either of the following:

 

  • As per Acquisition costs
  • As per net value
  • Or any manner defined by the user

pic13.png


Once the same is determined, a work Queue gets added:


pic14.png

pic15.png

  The same is then released in transaction AR31 for release of worklist:

pic16.png

 

pic17.png

 

The status changes to completed when the processing is complete

pic18.png


The accounting entry that gets generated on retirement is described below:

pic19.png

Since the asset was fully depreciated,  accumulated depreciation and asset account is fully reversed. The entire proceeds from sales is  taken as revenue. Revenue of100 EUR is distributed in proportion to the acquisition cost amongst the three assets that have been retired.

 

2.3  Mass Inter Company Asset transfer


Assets Transfer from one company code to another mainly happens in case of restructuring of an organization when a change in company code is necessitated. The standard transaction for executing this is ABT1N.  However when an enterprise desires to do a mass Inter company asset transfer in SAP,  the same can be made using the worklist functionality. Like retirement of assets, this involves creation of worklist and release of the same.

 

A worklist as described above is created using the transaction code AR01. All assets that have to be transferred are given in the selection criteria as shown below:

pic20.png

These assets are then added to the worklist as shown below:

pic21.png

In the selection screen that appears subsequently, the target assets to which the transfer has to be made is given. The transfer variants have to be selected based on the options available in the dropdown The transfer variant specifies the valuation method and the transaction type for posting an asset transfer:

pic22.png

As described above in retirement, a work queue gets added and the same has to be released in the transaction code AR31 as below:

pic23.png

 

pic25.png


Once the transfer is successful, acquisition cost and accumulated depreciation value becomes 0 in the books of the transferor company:


pic26.png

 

The entry that is passed at the time of retirement is as follows:

In the books of transferor company, Asset Account is credited and the accumulated depreciation account is debited.

In the books of the transferee company the reverse entry takes place.

 

The usage of worklist functionality for mass changes to asset master would involve an additional step, i.e. creation of Substitution Rule. These are described in Part II of this document-the link for which I shall update shortly

Service category wise report in Service tax

$
0
0

SERVICE TAX – CATEGORY WISE REPORTING

 

 

The list of service category for service tax purpose is given in the table.  These codes can be used in the assignment column ( any free fields in FB60 )  in the line item entry to get report on service tax category wise as required by the Service tax authorities.

 

 

SNO       CODE     DESCRIPTION   

 

 

1              ADV       ADVERTISING AGENCY

 

 

2              ADS        ADVERTISING SPACE OR TIME

 

 

3              ATS        AIR TRANSPORT OF PASSENGER

 

 

4              AIR         AIR TRAVEL AGENCY

 

 

5              APS        AIRPORT SERVICES

 

 

6              ARC        ARCHITECTS SERVICES

 

 

7              AMN     ASSET MANAGEMENT SERVICES

 

 

8              ATM      ATM OPERATIONS

 

 

9              AUS       AUCTIONEERS SERVICES

 

 

10           BFN        BANKING AND FINANCIAL

 

 

11           BTY         BEAUTY PARLOURS

 

 

12           BRD        BROADCASTING SERVICE

 

 

13           BES         BUSINESS AND EXHIBITION SERVICES

 

 

14           BAS        BUSINESS AUXILIARY SERVICES

 

 

15           BSS         BUSINESS SUPPORT SERVICES

 

 

16           CAB        CAB OPERATORS

 

 

17           CBL         CABLE OPERATORS

 

 

18           CHS        CARGO HANDLING SERVICES

 

 

19           CAC        CHARTERED ACCOUNTANTS

 

 

20           CLG        CLEANING SERVICES

 

 

21           CFA        CLEARING AND FORWARDING AGENCY

 

 

22           CTC        COMMERCIAL TRAINING & COACHING

 

 

23           COS        COMPANY SECRETARIES

 

 

24           CON       CONSTRUCTION OF RES. COMPLEX

 

 

25           CCS        CONSTRUCTION SERVICES ( COMMERCIAL /INDUSTRIAL BUILDINGS/ CIVIL STRUCTURES)

 

26           CER        CONSULTING ENGINEER

 

27           COR       CONTAINERS BY RAIL

 

28           CVN       CONVENTION SERVICE

 

29           COA       COST ACCOUNTANTS

 

 

30           COU       COURIER AGENCY

 

31           CRD        CREDIT CARD RELATED SERVICES

 

32           CRA        CREDIT RATING AGENCIES

 

33           CHA       CUSTOM HOUSE AGENT

 

34           DSN       DESIGN SERVICES

 

35           DSC        DEVELOPMENT AND SUPPLY OF CONTENT SERVICES

 

36           DRS        DREDGING SERVICES

 

37           DCS        DRY CLEANING SERVICES

 

38           CAI         ERECTION,COMMISSIONING AND INSTALLATION

 

39           EVS        EVENT MANAGEMENT SERVICE

 

40           FCS         FACSIMILE SERVICES

 

41           FDS        FASHION DESIGNER SERVICES

42           FDC        FORWARD CONTRACT SERVICES

43           FRA        FRANCHISE SERVICES

 

44           GIB         GENERAL INSURANCE BUSINESS

 

45           GTO       GOODS TRANSPORT OPERATORS

 

46           HFC        HEALTH CLUB AND FITNESS CENTER

 

47           ISS          INFORMATION TECHNOLOGY SOFTWARE SERVICE

 

48           ISD         INPUT SERVICE DISTRIBUTOR

 

49           IAX         INSURANCE AUXILIARY

 

50           IPR         INTELLECTUAL PROPERTY SERVICES OTHER THAN COPYRIGHT

 

51           IDS         INTERIOR DECORATORS

 

52           INC         INTERNET CAFE

 

53           ITS          INTERNET TELECOMMUNICATION SERVICE

 

54           LCR         LEASED CIRCUITS

 

55           LIS          LIFE INSURANCE SERVICES

 

56           MCM     MAILING LIST COMPILATION

 

57           MRS       MAINTENANCE OR REPAIR SERVICE

 

58           MGC      MANAGEMENT CONSULTANTS

 

59           ULI         MANAGEMENT OF INVESTMENT UNDER ULIP SERVICE

 

60           MAK      MANDAP KEEPER

 

61           MRA      MANPOWER RECRUITMENT AGENCY

 

62           MRK      MARKET RESEARCH AGENCY

 

63           MCA      MEMBERSHIP OF CLUBS

 

64           MNG     MINING SERVICES

 

65           OID        ONLINE INFORMATION AND DATA

 

66           OPS        OPINION POLL SERVICES

 

67           ODC       OUTDOOR CATERING

 

68           PKG       PACKAGING SERVICES

 

69           PGS        PAGER SERVICES

 

 

70           PSS         PANDAL OR SHAMIANA SERVICES

 

71           PGH       PHOTOGRAPHY SERVICE

 

72           PRT        PORT SERVICES

 

73           PCH        PROCESSING AND CLEARINGHOUSE SERVICE

 

74           PRS        PUBLIC RELATIONS SERVICE

 

75           RTA        RAIL TRAVEL AGENT

 

76           REA        REAL ESTATE AGENTS

 

77           CXS        COMMODITY EXCHANGE SERVICE

 

78           RCA        RECOVERY AGENT

 

79           RTI          REGISTRAR TO AN ISSUE

 

80           RIS          RENTING OF IMMOVABLE PROPERTY SERVICES

 

81           STC         SCIENTIFIC AND TECHNICAL CONSULTANCY

 

82           SEA        SECURITY AGENCIES

 

83           SMV      SERVICING OF MOTOR VEHICLES

 

84           STR         SHARE TRANSFER AGENT

 

85           SMS       SHIP MANAGEMENT SERVICE

 

86           SPC        SITE PREPARATION AND CLEARANCE

 

87           SRC        SOUND RECORDING SERVICE

 

88           SPN        SPONSORSHIP SERVICE

 

89           STA        STEAMER AGENT

 

90           STB         STOCK BROKER

 

91           SXS         STOCK EXCHANGE SERVICE

 

92           SWS       STORAGE AND WAREHOUSE SERVICE

 

93           STG        SUPPLY OF TANGIBLE GOODS FOR USE SERVICE

 

94           SEM       SURVEY AND EXPLORATION OF MINERAL

 

95           SUR        SURVEY AND MAP MAKING

 

96           TEL         TELECOMMUNICATION SERVICES

 

97           TGH       TELEGRAPH SERVICE

 

98           TSU        TELEPHONE SERVICES

 

99           TLX         TELEX SERVICES

 

100         TIC          TEST,INSPECTION, CERTIFICATION

 

101         TOU       TOUR OPERATOR

 

102         TCS         TRANSPORT BY CRUISE SHIPS

 

103         TGA       TRANSPORT OF GOODS BY AIR

 

104         TGP        TRANSPORT OF GOODS BY PIPELINE

 

105         GTA       TRANSPORT OF GOODS BY ROAD

 

106         TAO       TRAVEL AGENTS (OTHER THAN AIR/RAIL TRAVEL AGENTS)

 

107         TRP        TV OR RADIO PROGRAMME PRODUCTION

 

108         UWS      UNDER WRITERS

 

109         VTP        VIDEO TAPE PRODUCTION

 

110         WCS       WORKS CONTRACT SERVICES

 

 

In FBL3N Report the service category can be captured and using filter option the category wise report is possible. 

 

Sertax.jpg

 

 

        

 

                                                                                                                SELVAKUMAR.N


How to enter Budget / planning amount for profit centre using excel

$
0
0

This Document will give overview on how to to enter planning amount for profit center or How to enter Budget amount for profit centre USING EXCEL .

 

Using Excel we can upload planning/budget amount for profit center in SAP. After uploading this we can compare profit center with cost center and do variance analysis .This input will help us in taking control over profit center earning and can be used by management. This will involve following steps .

 

Initially we must prepare layout in format required to upload in SAP . Layout needs to be made in tcode 7KEC .one of format of layout in displayed in step 3 below .

 

1 Creation of file description

Tcode KP34PC

IN Tab "layout for profit center accounting " make sure to tick integrated excel after entering layout as we made above in Tcode 7KEC

This will help to generate excel in tab "default parameters "

New excel layout and file description get generated . This need to be saved separatly in excel so that can be used .

Untitled.png

 

2 File Description will get generated & same needs to entered at desired field in above Tcode

Verification of file description created can be checked out in Tcode 7KEX

Untitled.png

 

3 During saving in tcode KP34PC (step 1 above) excel layout gets generated that needs to be used .

In this excel layout we need to insert planning amount .

Tcode 7KEX used to upload excel in SAP

 

Untitled.png

 

 

4 Cross verify updation of planning amount in profit center

Will cross verify whether planning profit center amount has been uploaded in SAP

Will use Report Tcode KE5Y

Untitled.png

 

Untitled.png

 

Regards

kaushal Ghedia

Reason code configuration in SAP

$
0
0

Hello Forum,

 

While doing customer incoming payments, if we want to deduct and bank charges or any other deductions in standard SAP we have an option of reason code

configuration. By doing the above configuration the deductions will post to configured P&L GL account in configuration and clear the customer.

 

Customer open item before payment: 1500 $ (FBL5N)

 

1.jpg

 

Configuration of reason code configuration for bank charges:

 

Financial Accounting (New)--> Accounts Receivable and Accounts Payable--> Business Transactions--> Incoming Paymentsà Incoming Payments Global Settings--> Overpayment/Underpayment--> Define Reason Codes

 

Please create the same company code specific.

 

2.jpg

11.jpg

Define Accounts for Payment Differences

 

Financial Accounting (New)--> Accounts Receivable and Accounts Payable--> Business Transactions--> Incoming Payments--> Incoming Payments Global Settings--> Overpayment/Underpayment--> Define Accounts for Payment Differences

 

The account is P&L account and expense account in nature (400008).

4.jpg

 

Customer incoming payment with reason code: F-28

 

5.jpg

 

Now click on residual line items give the reason code and invoice amount excluding bank charges.

 

6.jpg

 

Click on document overview and simulate the document

 

12.jpg

Make sure that cost object has been maintained in OKB9 settings have been maintained for bank charges GL account.

 

8.jpg

 

After payment the customer line item display is as follows:

9.jpg

10.jpg

 

Regards,

 

Ravi

Importance of Tcode GWUL in customised report GR55 & translation of currency

$
0
0

Client usually make customized report and in that case testing of data takes place and many times testing gets correct but they miss out essential part required at time of using special purpose ledger is using Tcode GWUL .

GWUL is used for refreshing customized report made in report painter like trial balance , balance sheet , cashflow statement , segment reporting etc

This GWUL is used when transaction are taking place in foreign currency and reporting is required in some other currency . So essentiality is both currency should be different .

 

Tcode GWUL

1.png

 

I will explain from point of balancesheet where reports are extracted at any period of time .But exchange rates keeps on changing on daily basis in that case such balancesheet report need to be refreshed to latest exchange rates . This is where GWUl is used . GWUL refreshes Balancesheet at latest exchange rates and post difference to defined GL accounts called as translation difference account .

How to find Translation difference account?.Tcode GCW4Below screenshot shows that GL 32001 is where Translation dfference will be posted

Untitled.png.

 

Now Will check how this this exactly works

Will take balance sheet for period 6 FY2014

Make note of GL10001 in Company code 0070

Untitled.png

 

After some months there is again requirement for balancesheeet .We assume that no transation has been posted in between periods .

Will run GWUL for Period 9 Fy 2014 so as to refresh balancesheet to exchange rate available for Period 9 Fy 2014 .

This is how GWUL will show details .

1.png

 

Now will reopen Balncesheet for period 9 FY14

 


3.png

So now We can see balances are changed in GL 10001 and Balance sheet is tallied and balance is shifted to "TRANSLATION DIFFERENCE ACCOUNT"


Also we can check that translatn diff amount in after running GWUL above tallies with amount available in balancesheet .


 

Regards

kaushal Ghedia

Usage of Worklist Functionality in Asset Accounting-Part II

$
0
0

The first part of this document is explained under the Usage of Worklist Functionality in Asset Accounting-Part I  (. This document is a continuation to that document. The intent of this document is to explain the usage of worklist functionality in asset accounting for carrying out mass changes to the asset master.
The example used in this document is a basic scenario to explain the usage of Worklist functionality and the steps to be followed to carry out mass changes to asset master.
Mass changes to assets master could involve changes to any of the fields to Asset Master Data like terms of depreciation, changes in cost center, populating the master data with a field that was earlier not populated.
The use of worklist functionality to carry out the same involves
  1. Creation of substitution rule
  2. Creation of worklist
  3. Release of the worklist.
Thus we see that there is an additional step for creation of substitution rule for carrying out mass changes to the asset master.

The steps to carry out the same are described below.

The first step to make mass changes to an asset is to create a substitution rule to determine the new value that has to be populated in the asset master data. The substitution rule is created in transaction code GGB1:

pic1.png
Here we create a substitution rule “ABC” to ensure that all assets in a particular asset class are populated with a particular cost center.
pic2.png
In the substitution rule, we determine the value with which the field (here cost center) in the asset master data is to be populated.

pic3.png
The prerequisite for the substitution rule is defined here. Only when the conditions for the company code and cost center as defined below are met, will the substitution rule apply

pic4.png
  The field with which the cost center is to be updated is defined in the “Substitution” step below:
pic5.png
pic6.png
The substitution rule created above is assigned to the company code using the transaction code OA02:
pic7.png

The asset class for which changes in cost center has to be made is added to the worklist using the transaction code AR01


pic8.png


We select the option mass changes to asset master here:

pic9.png

 

Thereafter we select the substitution that was created for mass change and assigned to the company code in transaction OA02


pic11.png

 

Subsequently a work queue gets added.


pic12.png

Workqueue 000000948654 added

 

Then we release the work queue in transaction AR31 as indicated below:

pic13.png

 

pic14.png

 

Check the error log tab for errors if any


pic15.png

The asset master data will now show the new value for the cost center:


pic16.png

 

Thus we see that worklist functionality can be used to carry mass changes to the asset master. This can be used for various fields on a case to case basis depending upon the scenario.

How to Create a Transaction Variant

$
0
0

Main purpose of this T-Code is to customise any standard SAP transaction in a minimum time, by which a new version will be created of standard SAP T-code without any actual modification. It can be used in a way that if we dont want any bunch of users to view or enter any thing in a particular field then we can do this without going for any customization.

 

The below Document will give steps for using Transaction Variant for Vendor Master Creation [FK01]:

 

  1.   Enter T-Code 'SHD0':

Enter in Transaction Code – FK01

Enter in Transaction Variant – ZFK01 and then on create button

 

transaction.jpg

 

 

 

  1.   In the next screen T-Code FK01 will be opened in recording mode.

Here we are going to hide Reference Vendor Tab, so enter some default value '1800177'.

Then click enter and new pop up screen will be opened.

 

transaction.jpg

 

 

 

  1.   In the confirm screen entries, we can choose what we want to do in that screen. Enter screen variant short txt as 'Testing' and tick on Invisible Tab to hide Reference Vendor from the screen.

Then Click on Menu Functions.

 

transaction.jpg

 

 

 

 

4. After clicking on 'Menu Functions' tab, a screen will be opened, in that select Vendor → EANZ (Display) and then De-activate button. This will now be deactivated and it will be in yellow. Now Click on Enter Tab.

 

transaction.jpg

 

 

5. After above step on confirmation, click on 'Exit and Save' Tab.

 

transaction.jpg

 

 

 

  1.   Now system will ask for saving the Transaction Variant. It has to be saved in either a New Request of can be saved as 'Local Object'.

 

transaction.jpg

 

transaction.jpg

 

 

  1.   We can now test the transaction Variant in the Initial Screen by Clicking on 'Test' Button.

 

transaction.jpg

 

 

Assigning Transaction Variant ot Transaction Code:

 

  1.   Run T-Code 'SE93'. Enter Transaction Code – 'ZFK01_tcode' and Click on 'Create' Tab.

 

transaction.jpg

 

 

  1.   In next screen enter short text and select Radio Button of 'Transaction with variant (variant transaction) and click on Enter.

 

transaction.jpg

 

3. In next screen, enter text in 'Transaction' & 'Transaction Variant' field.

 

transaction.jpg

 

 

 

By this now a new Transaction Code – 'ZFK01_TCODE' is available with Reference → Vendor Field as Invisible.

 

transaction.jpg

 

transaction.jpg

 

We can see from above that Reference → Vendor field is Invisible and a default Vendor is selected.

Difference between "display line items" flag marked and not marked (Entry view and GL view)

$
0
0

Hi Colleagues,

 

I created two scenarios below with line item display flag and without this flag to explain this function. But first, you've to understand the difference in the entry view and GL view.

 

The entry view is where you can see documents in the subledgers AP and AR. The GL view is where you can see these documents independent of subledgers. Always will be displayed by GL.

 

When a GL account is created, you've the option to mark the "Dislpay line items" checkbox. Technically, if the flag is marked, these line items will be copied to subledgers or entry view. If does not has the flag, e.g BSIK or BSAK (opened line items and cleared line items tables for vendor) won't displayed this line items and FBL3N or FAGLL03 in the entry view can't be displayed. BSIK and BSAK tables for vendor side, this can be applied for customer o GL side.

 

FBL3N has only entry view. FAGLL03 has two types of views: entry view and GL view. FAGLB03, FS10 and FS10N are displayed the balance independent of the flag. But to display line items by FS10 and FS10N. i.e, transactions that are used with entry view will be checked in the master data GL account if the flag is marked or not. If does not marked, line item won't appears.


In the FAGLL03 tcode when GL view is selected is independent of flag in the data master GL account because this transaction research BSEG table to find line items. This happens too with FAGLB03 to dislplay line item because this transaction use only GL view.

 

Check the screenshots below:

 

Without flag GL account 2010000000 and with entry view:


SKB1_line_item_display_1.jpg

FAGLL03

 

ScreenHunter_002.jpg

 

FBL3N

 

ScreenHunter_003.jpg

 

Without flag GL account 2010000000 and with GL view:


ScreenHunter_001.jpg

 

With flag GL account 2010001000 and entry view:

 

FBL3N

ScreenHunter_004.jpg

 

FAGLL03

 

ScreenHunter_005.jpg

 

If you created a GL account without this flag and after some time you want to activate it, you've to run RFSEPA01 program or FAGL_ACTIVATE_IT tcode. This transaction will copy the line items from BSEG table to BSIK and BSAK tables for vendor side. But, also can be applied for customer or GL side.

 

But before to run or activate this flag, read the program documentation.

 

 

JPA

How to Create a Transaction Variant

$
0
0

Main purpose of this T-Code is to customise any standard SAP transaction in a minimum time, by which a new version will be created of standard SAP T-code without any actual modification. It can be used in a way that if we dont want any bunch of users to view or enter any thing in a particular field then we can do this without going for any customization.

 

The below Document will give steps for using Transaction Variant for Vendor Master Creation [FK01]:

 

  1.   Enter T-Code 'SHD0':

Enter in Transaction Code – FK01

Enter in Transaction Variant – ZFK01 and then on create button

 

transaction.jpg

 

 

 

  1.   In the next screen T-Code FK01 will be opened in recording mode.

Here we are going to hide Reference Vendor Tab, so enter some default value '1800177'.

Then click enter and new pop up screen will be opened.

 

transaction.jpg

 

 

 

  1.   In the confirm screen entries, we can choose what we want to do in that screen. Enter screen variant short txt as 'Testing' and tick on Invisible Tab to hide Reference Vendor from the screen.

Then Click on Menu Functions.

 

transaction.jpg

 

 

 

 

4. After clicking on 'Menu Functions' tab, a screen will be opened, in that select Vendor → EANZ (Display) and then De-activate button. This will now be deactivated and it will be in yellow. Now Click on Enter Tab.

 

transaction.jpg

 

 

5. After above step on confirmation, click on 'Exit and Save' Tab.

 

transaction.jpg

 

 

 

  1.   Now system will ask for saving the Transaction Variant. It has to be saved in either a New Request of can be saved as 'Local Object'.

 

transaction.jpg

 

transaction.jpg

 

 

  1.   We can now test the transaction Variant in the Initial Screen by Clicking on 'Test' Button.

 

transaction.jpg

 

 

Assigning Transaction Variant ot Transaction Code:

 

  1.   Run T-Code 'SE93'. Enter Transaction Code – 'ZFK01_tcode' and Click on 'Create' Tab.

 

transaction.jpg

 

 

  1.   In next screen enter short text and select Radio Button of 'Transaction with variant (variant transaction) and click on Enter.

 

transaction.jpg

 

3. In next screen, enter text in 'Transaction' & 'Transaction Variant' field.

 

transaction.jpg

 

 

 

By this now a new Transaction Code – 'ZFK01_TCODE' is available with Reference → Vendor Field as Invisible.

 

transaction.jpg

 

transaction.jpg

 

We can see from above that Reference → Vendor field is Invisible and a default Vendor is selected.


Vendor Invoice, payment & Manual Bank Reconciliation process in SAP

$
0
0

Hi Forum,

 

Please follow the below vendor invoice, payment and Manual bank reconciliation process step by step in SAP.

 

Vendor Invoice: (FBL1N)

1.jpg

 

Accounting Entry:

 

IT Outsourcing Expenses DR

TO Vendor CR

 

Payment through APP (F110):

2.jpg

3.jpg

4.jpg

 

Check payment variant:

5.jpg

6.jpg

7.jpg

 

Edit proposal:

 

8.jpg

9.jpg

Payment run:

10.jpg

11.jpg

 

Accounting Entry at the time of payment:

 

Vendor Account DR

TO Check out Account CR

 

After payment the vendor line item display is as follows:

12.jpg

 

Check out account GL Display: 4000 $ Open balance before manual bank reconciliation

13.jpg

 

Transaction code: FF67

Opening and closing balance before bank file execution.

 

14.jpg

 

In FF67 front screen give the bank key, bank account number of the house bank.

15.jpg

Press enter and give the checkout transaction which was created, value date, amount and bank reference

16.jpg

Click on save

17.jpg

Now click on save to post the statement.

 

18.jpg

 

Now execute the scheduled job.

Transaction code: SM35

19.jpg

20.jpg

 

Now execute in fore ground.

21.jpg

Main bank account (100001) is crediting from the configuration.

22.jpg

23.jpg

24.jpg

25.jpg

The checkout GL line items after manual bank file execution in SAP.

26.jpg

 

Accounting Entry:

 

Check out Account DR

TO main Bank Account CR

27.jpg.

 

Happy learning, wish you all the best.

 

Regards,

Ravi

Leveraging on SAP Excel Integration in Maintaining Exchange Rates

$
0
0

It is a standard process for finance users to maintain the exchange rates for foreign currency transactions in SAP. The frequency (i.e. daily, weekly, or monthly) of update for exchange rates can vary per company and it largely depends on the company’s practice.

 

The practice of most companies is to maintain the foreign currency exchange rates directly in the currency exchange table.

Figure 1.png

Figure 1. Screenshot of Currency Exchange Rates (t-code: S_BCE_68000174)

 

While it is not too difficult to maintain the exchange rate table for infrequent maintenance (e.g. monthly) and for fewer currency pairs, finance users will request for the maintenance of exchange rates to be uploaded from a file (e.g. excel file) if the frequency and volume increases. Most consultants will suggest developing a customized upload tool for the user.

 

Little known to most, SAP provides an off-the-shelf solution in maintaining market data in the SAP using Excel Integration Tool. The SAP standard program is RFTBDF_OLE. The program is intended for the SAP Financials - Treasury application for update of market data such as currencies, securities prices, interest rates,  and others. The program is flexible enough that it can be used by finance users to update the exchange rate table using Microsoft excel as upload tool.

 

So, how difficult is it to upload the using the SAP standard application? It’s fairly simple and easy 2-step process: (1) Preparation of excel template and (2) Uploading to SAP.

 

1- Prepare the Excel Template


    1. Maintain Exchange Rate entries in the Excel Template based on SAP required format

 

The formatting and explanation of the fields for the excel template are quite straight forward.


Below is the field description and comments as published in the SAP documentation.

 

Field

Column Description

Field Length

Required (R) / Empty (E)

Comments

Example Data

1

Class

2

R

Fixed Value: 01 - Exchange Rates

01

2

Key 1

20

R

From Currency

EUR

3

Key 2

20

R

To Currency

USD

4

Cat

15

R

Exchange Rate Types

M

5

Date

8

R

Valid From Date

1/1/2014

6

Time

6

E

Time of Value Data

 

7

Valuation

20

R

Exchange Rate

1.1876

8

Currncy

20

E

Not applicable

 

9

"Fr" ratio

7

R

Translation Ratio From

1

10

To factor

7

R

Translation Ratio To

1

11

Addt.

5

E

Not Applicable

 

12

Status

2

E

Error Status

 

13

Error message

80

E

Error Message

 

 

Below is a screenshot of the excel format of the excel template

Figure 2.png

 

          b. Ensure to save the workbook in 1997 – 2003 that is it must have an “.xls” as extension.

Figure 3.png

 

2. Upload the file in SAP

 

          a. Access Transaction Code: TBEX

 

          b. In the Market Data Transfer from Spreadsheet Initial Screen, Select the following:

    • Currencies (Market Data)
    • Exchange Rates (Direct Quotation or Indirect Quotation)

     

    Figure 4.png

     

              c. In the Spreadsheet Parameters, choose the excel template file in the user’s desktop

     

    Figure 5.png

     

              d. Click on Icon icon 1.png to start the transfer

     

              e. System will load the file in the spreadsheet tab. Note that the Status and Error will be blank

    Figure 6.png

              f. Click on Import Market Data icon 2.png

             

              g. In the spreadsheet tab, the status will update as OK.

     

    You’re done. Users can then verify the exchange rates updated in the system. It's simple and easy step leveraging SAP excel integration. 

    Explanation for Delta Logic in Foreign Currency Revaluation

    $
    0
    0

    Foreign currency revaluation is done to revalue the AP/AR and other GL accounts (e.g. bank GL account) balances in foreign currency in order to bring them to the market value during the month end closing rate. The revaluation will be done for all open items and account balances in foreign currency. The practice of foreign currency revaluation is required as per IAS 21 as well as local GAAP requirement.

     

     

    It is a practice to revalue the AP/AR and other account balances at month-end rate or closing rate at the last day of the month. Subsequently, these transaction posting is reversed at the first day of the following month.


    Figure 1 is a simple illustration of the accounting flow of FX revaluation. Pls. note that the illustrations on the accounting flow are given based on the scenario of having an open payable item transaction currency in USD and the functional currency of the company is in SGD, and the fiscal year of the company is Jan-Dec.

    Figure 1.png

    Figure 1. Illustration of accounting flow for FX revaluation

     

    However, for certain countries like Korea and Hungary, it is not allowed to reverse the revaluation to the following year (i.e. 01 Jan XXXX). SAP has provided the Delta Logic Functionality for the Foreign Currency Revaluation. So, how does this delta logic functionality works accounting-wise?


    The Delta logic can be activated in SAP configuration. The focus of the document is to explain the accounting flow and FX revaluation execution for this document, but before proceeding we can touch on briefly the basic configuration requirement for Delta Logic. Figure 2 is the activation of Delta Logic in FX revaluation in SAP.

     

    Figure 2.png

    Figure 2. Screenshot of the Delta Posting Logic.


    There are several tickbox for the table. Below is the explanation of the configuration as per SAP documentation:

    1. 1- “+” – If this switch is set, a delta logic is used for the foreign currency valuation.
    2. 2- “Cl.Date” – If this indicator is set, the clearing date of the valuated item is used for the reversal postings.
    3. 3- “Mon.Rev.” - Allows the reversal of mid-fiscal year valuation within delta logic. If you set this indicator, you will be able to specify whether the reversal of valuation postings is possible in the Foreign Currency Valuation report in conjunction with the delta logic.


    Necessary configuration still needs to be maintained (for example, account determination, GL master data settings, Valuation Areas, and others); the intention of the document is to explain the accounting flow and not serve as a configuration guide.


    Upon activation of the Delta Logic activated in FX revaluation, there will be a slight change in the selection screen. That is, two new fields will show to determine whether the revaluation is “Year-End Revaluation” or “Mid-Year Revaluation”. Finance will need to select “Year-End Closing Valuation” for Dec; Select “Mid-Fiscal Year Valuation” for the other months (e.g. Jan – Nov).


    Figure 3.png


    Figure 3. Screenshot of the changes in the FX revaluation selection screen for Delta Logic.

     

    To illustrate the accounting flow for Delta Logic, pls. refer to Figure 4 below. At year-end closing, the open AR is revaluated based on Dec 31, 2012 closing rate of @1.30. The revaluation will result to unrealized exchange loss of 50 SGD. Since it is year-end closing, there will be no reversal posting on Jan 1, 2013. Assuming no payment has been received for Jan. The same open item will be revaluated again on Jan 31, 2013 with a new month-end exchange rate of 1.32 SGD.

    Figure 4.png

    Figure 4. Illustration of accounting flow for Delta Logic of FX revaluation

     

    SAP system will consider December’s revaluation in calculating the current month revaluation. In the FX revaluation report, finance users will be able to see the following columns:

    1. Old Revaluation – latest revaluation amount for the open item
    2. New Revaluation – New revaluation based on current month
    3. Amount to be Posted – Difference (or Delta) amount


    Figure 5 is a screenshot of the FX report and where users can see the difference.

     

    Figure 5.png

    Figure 5. Sample screenshot from SAP of FX revaluation Report


    Continuing on the same flow, the subsequent month posting is shown in Figure 6. Since this is not a year-end revaluation, the revaluation will

    be reversed on the 01-Feb. The customer made a payment for the invoice @ 1.37 on Feb 15, 2014; the corresponding realized exchange gain of 20 SGD will be posted. Subsequently, at month end revaluation, the reversal posting will be posted accordingly.

    Figure 6.png

    Figure 6. Illustration of accounting flow for Delta Logic of FX revaluation (cont)

     

    In SAP FX revaluation report, there will be an icon called “Cleared Items” and within this report, finance will be able to see the reversal of the revaluation for the cleared item (Figure 7).

    Figure 7.png

    Figure 7b.png

    Figure 7. FX revaluation Screenshot of Cleared Items and its report.


    A variant in the accounting flow is that the reversal of unrealized gain/loss for the payable will be posted at the time payment clearing. It can be done also just by selecting the indicator “Cl.Date”  in the configuration.


    In summary, this is marked improvement from the previous versions of the program. SAP has enhanced flexibility on the features and functionality in order to meet the different legal and reporting for Finance users.

    Cross-Company/Inter-company transactions

    $
    0
    0

    Cross-Company/Inter-company transactions

     

     

    Several company codes are involved in a cross-company code transaction. In a cross-company code transaction, the system posts a separate document with its own document number in each of the company codes.

    Individual documents are linked by a common cross-company code number. The system generates line items automatically (receivables and payables arising between company codes) in order to balance the debits and credits in each document.

     

    At times one company code makes purchases on behalf of another company code or makes payment on behalf of another company code. This needs entries to be passed in both company codes.

    If cross company code settings are done, entry in one company code would generate the entry in the other company code also.

    In this example, we have already two company codes 1009 and 1011 in country USA.

    1.1 Check whether Doc type SA allows cross company postings

    Via Menus

    IMG(SPRO)-->Financial Accounting( new) --> Financial Accounting Global Settings (New) --> Document  --> Document Types --> Define Document types for Entry View   

    Via Transaction Code

    OBA7

    Select Position button and give Document type SA and press Enter

    Make sure Document type SA allows Inter-company postings

    Doctype.jpg.png

     

     

    1.2 Create Clearing G/L account in both company codes in FS00

    Create below G/L accounts in respective company codes

    GL.jpg

     

     

    1.3 Prepare Cross company code Transactions

    Via Menus

    IMG --> Financial Accounting --> General Ledger Accounting--> Business transactions--> Prepare cross-company code transactions

    Via Transaction Code

    OBYA

     

    CC.jpg

       Provide below details and save Click on Save

    crosscocode.jpg

    Note :Alternatively, you can use Customer and vendor Posting Keys and give Inter-company Customer and Vendor numbers

     

     

     

    1.4 Prepare Cross company code for Manual Payments

    Via Menus

    IMG -->Financial Accounting -->Accounts Receivables and Payables --> Business transactions--> Outgoing payments --> Manual Outgoing payments-->Prepare Cross Company code for manual payments

    Via Transaction Code

    OB60

    Click on New Entries

    manual.jpg

    Click on Save

     

    1.5 Prepare Cross company code for Automatic Payments

    Via Menus

    IMG--> Financial Accounting--> Accounts Receivables and Payables--> Business transactions --> Outgoing payments--> Automatic Outgoing payments -->Payment method/Bank Selection for Payment Program--> setup all company codes for payment transactions

    Via Transaction Code

    FBZP

    Select company code 1011 (second created Company code) and give below details:

    fbzp.jpg

    Click on Save

     

     

    1.6 Post a cross company transaction

    Via Menus

    Accounting --> Financial Accounting--> Accounts Payables --> Document Entry     ----> Invoice

    Via Transaction Code

    FB60

    Provide below details

    FB60.jpg

    Make sure to use co code 1009 on the header and co code 1011 on the line item.

    Select Simulate and then Save

    CCDoc.jpg

    Click on Continue. Cross Company code document is posted.

     

    To Display the cross company Document

    Via Menus

    Accounting à Financial Accounting --> General Ledger--> Documentà Cross Company code transaction   -->Display

    Via Transaction Code

    FBU3

    Provide Cross company code document number or select from document list

    CCDoc.jpg

    Press Enter

    CCDoc.jpg

    Other Cross Company transactions i.e. Change/Display Reverse Cross Company document

    CCtcode.jpg

     

    1.7 Process Manual payment on behalf of other company code

    Via Menus

    Accounting --> Financial Accounting --> Accounts Payable --> Outgoing Payment --> Post

    Via Transaction Code

    F-53

    Prerequisite: Make sure that there are some open items for a vendor in company code 1011 or process a vendor invoice in 1011 using FB60/F-43

    fbl1n.jpg

    Go to F-53 and provide the below details

    f-53.jpg

    Click on Process Open Items and Select the invoice to be paid

    f-53-2.jpg

    Document-->Simulate-->Save

    CCDoc.jpg

    Note : Alternatively, you can run Automatic Payment Program (F110) as well.

     

     

    Hope this document helps

     

    Best Regards ,

    Venkat Emani

    Validation in Postal Code in Vendor / Customer Master

    $
    0
    0

                    Postal code is a unique data more helpful to track any address.     But in customer / vendor Master data often either  user skips this fields or fill something irrelevant if it supposed to be mandatory.     To create a validation rule for postal code I suggest a simple solution which an ABAPER can do without much effort.

     

     

                    The first 2 digit of the postal code represents the State as given below :

     

     

      First 2
      Digits of PIN

      Circle

      11

      Delhi 

      12 and 13

      Haryana

      14 to 16

      Punjab

      17

      Himachal Pradesh

      18 to 19

      Jammu & Kashmir

      20 to 28

      Uttar Pradesh and Uttaranchal

      30 to 34

      Rajasthan

      36 to 39

      Gujarat

      40 to 44

      Maharashtra

      45 to 49

      Madhya Pradesh and Chattisgarh

      50 to 53

      Andhra Pradesh

      56 to 59

      Karnataka

      60 to 64

      Tamil Nadu

      67 to 69

      Kerala

      70 to 74

      West Bengal

      75 to 77

      Orissa

      78

      Assam

      79

      North Eastern

      80 to 85

      Bihar and Jharkand

      90 to 99

      Army Postal Service (APS)

     

    Except 90- 99  all the ranges are possible values in postal code.    The “ Region”  field is used to capture the State.    The Pincode already entered by user can be verified by the Region selected by the user . 
    For example  

     

     

    First 2 digit of Pincode 60,61,62,63,64  are possible values for Region = 22  ( ie. Tamilnadu )

     

     

    This simple validation will be more useful even though not cent percent accuracy to some extent validate the data entered.  

     

     

    I invite all to improve the validation further towards more accuracy.

     

     

     

    Selvakumar.N

    Viewing all 366 articles
    Browse latest View live


    <script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>