SAP step by step

SAP EDI Inter-Company Billing - Automatic Posting To Vendor Account

2008-03-20T22:46:00.016+07:00

Inter-Company Billing - Automatic Posting To Vendor Account (SAP-EDI)

Automatic posting to vendor account is done by EDI. In our case where both companies
are proccessed in the same system (& client), it is sufficient to create Idoc.
This proccess requires several steps:
1. Creating a Customer to represent the receiving Company.
2. Creating a Vendor to represent the supplying company.
3. Creating a Port
4. Maintain an Output Type
5. Creating a Logical Address
6. Creating a Partner Profile for both Customer & Vendor
7. The relevant MM customizing is maintained.
8. The relevant FI customizing is maintained.

1. Creating a Customer to represent the receiving Company.
The customer has already been created (XD01) for the purpose of Intercompany
processing and entered in the approperiate transction in customizing (Sales and
Distribution à Billing à Intercompany Billing à Define Internal Customer Number By
Sales Organization).

Note: The cutomer has been created in the supplying company code.
The organizational data in this case is:
Supplying Company Code: 1180
Supplying Plant: 1180
Supplying Sales Organization: 1180
Supplying Distribution Channel: 01
Supplying Division: 00
Receiving Company Code: 3100
Customer representing the receiving Company Code: P3100

2. Creating a Vendor to represent the supplying company.
The Vendor is created with the standard transaction (XK01).
Note: The Vendor is created in the receiving Company Code. The organizational data in
this case is the same as above.

Vendor representing the supplying Company Code: P1180
NOTE: There is NO need to “connect” vendor to customer in the control screen.

3. Creating a Port
Tools à Business Communication à IDoc Basis à Idoc à Port Definition (T. Code WE21)
Maintain Transactional RFC: (Choose Transactional RFC and press the create icon).
A dialog box will open asking whether you want the system to generate an automatic
name or whether you wish to use your own name.

Port name: Automatically generated
Version: 4.x
RFC destination: PLD (This was defined by the basis people).

4. Maintain output type

Output Type RD04 - Invoice Receipt MM is a special function, responsible for the execution of the Idoc and will be entered in the Partner Profile later on.

Output type RD04 is maintained: Img: Sales and Distribution -> Basic functions -> Output control -> Output Determination -> Output Determination Using the Condition Technique -> Maintain Output Determination for Billing Documents à Maintain Output Types (T. Code V/40).

Partner functions

Sales and Distribution -> Basic Functions -> Output Control -> Output Determination à
Output Determination Using the Condition Technique -> Maintain Output Determination
for Billing Documents.

Assign Output Types To Partner Functions

Maintain Output Determination Procedure

Assign Output Determination Procedures

Master Data
Maintain output Master Data
Logistics -> Sales and Distribution -> Master Data -> Output -> (T. Code VV31)

5. Create Logical Address
Img: Sales and Distribution -> Billing à Intercompany Billing -> Automatic Posting To
Vendor Account (SAP-EDI) -> Assign vendor. (T. Code WEL1)

Logical address 1180P3100 is made of the supplying Company Code (1180) and the
receiving Customer (P3100).

Note: If the receiving Customer is a numeric number you must add zeros between the
Company code and Customer number so the Logical Address will be 14 digits.
E.g if the customer number was 3100, than the logical address would have been
11800000003100 as can be seen in the second line.
(In our case the customer is an alpha numeric number so the second line was not necessary. It was created just for this documentation and was not saved)

The Logical address is completed when the receiving Company Code and the Vendor are
entered in the detail screen.

It is also necessary to activate the account assignment.

IMG: Sales and Distribution -> Billing à Intercompany Billing -> Automatic Posting To
Vendor Account (SAP-EDI) -> Activate account assignment.

6. Creating a Partner Profile for both Customer & Vendor
Tools à Business Communication -> IDoc Basis -> Idoc -> Partner Profile (T. Code
WE20)

Customer:
Put cursor on Partner type KU and press create.
Enter typ, Agent & Lang,
SAVE

Press in outbound paratrs. Section, to maintain detail screens
The following screen will appear.

Enter the following data in the appropriate fields:
Partn.funct. BP
Message type INVOIC
Message Code FI
Receiving port A000000001
Basic Type INVOIC01

Press enter and the screen will change to the following:

Enter PacketSize 1

Go to the Message Control tab press and enter the data as specified in the following
screen.

You can repeat the process for cases where invoice verification is done against purchase
order. in this case enter MM in “message code field.

As you can see the only difference between the FI & MM invoice is in the message code
and output type.

NOTE: You cannot use output type RD04 again therefore you must copy it in
customizing to another output type (in this case RD00)

Vendor
Follow the same procedures but maintain the inbound parameter Screen as follows:

7. FI CUSTOMIZING
Financial Accounting à Accounts Receivable and Accounts Payable à Business
Transactions -> Incoming Invoices/Credit Memos -> EDI -> Enter Program Parameters
for EDI Incoming Invoice (T. Code OBCE)

Make sure to maintain posting types, tax code and invoice doc.type.

Use KR when not using purchase order & RE when using purchase order.

Assign Company Code for EDI Incoming Invoice

By leaving the field CoCD blank, all company codes are available.

Assign G/L Accounts for EDI Procedures (T. Code OBCB)

P1180 = Vendor

3100 = Company Code of receiving company (of customer)

NOTE:
G/L account should not be connected to CO. Assign Tax Codes for EDI Procedures (T.Code OBCD) It is necessary to match the output tax from the sales order to the input tax.

Tax type = Output Tax

Tx = Input Tax

Accounting -> Financial Accounting -> General Ledger -> Master Records -> Individual
Processing -> Centrally (T.Code FS00)

G/L account no. = account number that was entered in transaction OBCB (page 24)
Tax category must allow for input tax.

Make sure manual posting is allowed for the G/L account. (“Create/Bank/Interest”
screen).

TEXT
In many cases the G/L account has been configured so that text is mandatory. This could
be either Header Text or Item Text.

Header Text
No special configuration is necessary. Just enter text in the “Header note”. You may use
the following access sequence.

Item Text
It is necessary to implement a userexit in order to fill the item text field. Detailed
instructions are found in note 39503

8. MM Customizing:
Make sure the Unit of Measure’s ISO Codes are configured correctly.
General Settings à Check units of measurement (T. Code CUNI)

Optional MM Customizing:
NOTE: This is only necessary for logistics invoice verification.
Materials Management à Logistics Invoice Verification à EDI à Enter Program
Parameters

Monitoring
There are several transaction that allow you to monitor the IDoc. First you need to know
the IDoc number. You can see the IDoc number in the processing log in the “Header
output” screen in the billing document.

You can use transaction WE02 or WE05. Enter the IDoc number in the selection screen. If you have an error in the IDoc, you could analyze it with transaction WE19

Copy or Upload Excel Journal Entry to SAP

2008-03-08T23:16:00.000+07:00

SAP F.02 Copy from .XLS Excel Journal Entry

You can copy journal entries from Excel (.xls) and & paste them into SAP FB50 and F-02.

-when in FB50, fill out the required header rows,
-then choose menu path ENVIRONMENT -> COMPLEX POSTING (F6)

-Click "FAST DATA ENTRY" button this will give you the old GL fast entry screen which have 20 journal lines

or faster way is to go to SAP T-code F-02 directly.

If you can shrink your windows screen controls, you should be able to double the number of entry lines available. (depending on your screen resolution)

To move from cell to cell in Fast entry screen , use TAB key instead of "Enter" .

SAP F-02 fast entry display more journal lines and for allocating Debit or Credit journal entries , you enter posting keys in your excel sheet and copy manually to SAP F.02 screen.

If it is regular , you may create a program to upload excel data (.xls) to SAP.
There are two function modules you can use:
(1)'ALSM_EXCEL_TO_INTERNAL_TABLE'
(2) 'KCD_EXCEL_OLE_TO_INT'.
Very similar but the first function module (ASLM) used in for foregroundprocessing

Example from Marc Hoffmann
*Internal table to receive excel data
Data: Begin of in occurs 0.
include structure ALSMEX_TABLINE.
Data: End of in.

*internal table with result (your 3 field-table)
Data: begin of ex occurs 0,
f01(32), "max
f02(32),
f03(32),
.....
End of ex.

Data: fname(10).
Field-symbols: .

* so now you call the function to receive the data from EXCEL into table IN
* after that:
Fname = 'EX-F'.
Loop at in. "per column one line entry
at new row. Clear: ex. Endat.
move in-col+2 to fname+4(2).
assign (fname) to .
move in-value to .
at end of row.
append ex2.
Clear: ex.
endat.
Endloop.
* result: your table EX is filled matching your EXCEL sheet
That works flexible for whatever number of column you will receive (in my example max 99).

If you use ALSM_EXCEL_TO_INTERNAL_TABLE
Then:
parameters: p_fname LIKE rlgrap-filename
default 'C:\temp\cpv25000.xls' obligatory.

form upload_one_sheet.
Data: st_col type i value 1,
st_row type i value 1,
en_col type i value 90,
en_row type i value 9999. "max number of lines
CALL FUNCTION 'ALSM_EXCEL_TO_INTERNAL_TABLE'
EXPORTING
FILENAME = p_fname
I_BEGIN_COL = st_col
I_BEGIN_ROW = st_row
I_END_COL = en_col
I_END_ROW = en_row
TABLES
INTERN = in
EXCEPTIONS
INCONSISTENT_PARAMETERS = 1
UPLOAD_OLE = 2
OTHERS = 3.
case sy-subrc.
when 0.
when 1. message e016(38) with 'Inconsistent parameters'.
when 2. message e016(38) with 'Error upload OLE'.
when others. message e016(38) with 'Error'.
endcase.
endform.

SAP SD related transaction codes

2008-03-08T02:43:00.005+07:00

SAP SD related transaction codes

Customer
XD01 Create Customer (Centrally)
XD02 Change Customer (Centrally)
XD03 Display Customer (Centrally)
XD04 Customer Changes (Centrally)
XD05 Block customer (centrally)
XD06 Mark customer for deletion (centr.)
XD07 Change Customer Account Group
XD99 Customer master mass maintenance
XDN1 Maintain Number Ranges (Customer)

Vendor
XEIP Number range maintenance: EXPIMP
XK01 Create vendor (centrally)
XK02 Change vendor (centrally)
XK03 Display vendor (centrally)
XK04 Vendor Changes (Centrally)
XK05 Block Vendor (Centrally)
XK06 Mark vendor for deletion (centrally)
XK07 Change vendor account group

Sales Order
VA00 Initial Sales Menu
VA01 Create Sales Order
VA02 Change Sales Order
VA03 Display Sales Order
VA05 List of Sales Orders
VA07 Compare Sales - Purchasing (Order)
VA08 Compare Sales - Purchasing (Org.Dt.)

Inquiry
VA11 Create Inquiry
VA12 Change Inquiry
VA13 Display Inquiry
VA14L Sales Documents Blocked for Delivery
VA15 Inquiries List

Quotation
VA21 Create Quotation
VA22 Change Quotation
VA23 Display Quotation
VA25 Quotations List
VA26 Collective Processing for Quotations

Contract
VA41 Create Contract
VA42 Change Contract
VA42W Workflow for master contract
VA43 Display Contract
VA44 Actual Overhead: Sales Order
VA45 List of Contracts
VA46 Coll.Subseq.Processing f.Contracts

Item Proposal
VA51 Create Item Proposal
VA52 Change Item Proposal
VA53 Display Item Proposal
VA55 List of Item Proposals
VA88 Actual Settlement: Sales Orders

Delivery (Outbound)
VL00 Shipping
VL01 Create Delivery
VL01N Create Outbound Dlv. with Order Ref.
VL01NO Create Outbound Dlv. w/o Order Ref.
VL02 Change Outbound Delivery
VL02N Change Outbound Delivery
VL03 Display Outbound Delivery
VL03N Display Outbound Delivery
VL04 Process Delivery Due List
VL06 Delivery Monitor
VL06C List Outbound Dlvs for Confirmation
VL06D Outbound Deliveries for Distribution
VL06F General delivery list - Outb.deliv.
VL06G List of Oubound Dlvs for Goods Issue
VL06I Inbound Delivery Monitor
VL06IC Confirmation of putaway inb. deliv.
VL06ID Inbound Deliveries for Distribution
VL06IF Selection inbound deliveries
VL06IG Inbound deliveries for goods receipt
VL06IP Inbound deliveries for putaway
VL06L Outbound Deliveries to be Loaded
VL06O Outbound Delivery Monitor
VL06P List of Outbound Dlvs for Picking
VL06T List Outbound Dlvs (Trans. Planning)
VL06U List of Uncheckd Outbound Deliveries
VL08 Confirmation of Picking Request
VL09 Cancel Goods Issue for Delivery Note
VL10 Edit User-specific Delivery List
VL10A Sales Orders Due for Delivery
VL10B Purchase Orders Due for Delivery

Customer management
FD01 Create Customer (Accounting)
FD02 Change Customer (Accounting)
FD02CORE Maintain customer
FD03 Display Customer (Accounting)
FD04 Customer Changes (Accounting)
FD05 Block Customer (Accounting)
FD06 Mark Customer for Deletion (Acctng)
FD08 Confirm Customer Individually(Actng)
FD09 Confirm Customer List (Accounting)
FD10 Customer Account Balance
FD10N Customer Balance Display
FD10NA Customer Bal. Display with Worklist
FD10NET Customer Balance Display
FD11 Customer Account Analysis
FD15 Transfer customer changes: send
FD16 Transfer customer changes: receive
FD24 Credit Limit Changes
FD32 Change Customer Credit Management
FD33 Display Customer Credit Management
FD37 Credit Management Mass Change

Pricing
V/03 Create Condition Table (SD Price)
V/04 Change Condition Table (Sales pr.)
V/05 Display Condition Table: (Sales Pr.)
V/06 Condition Categories: SD Pricing
V/07 Maintain Access (Sales Price)
V/08 Conditions: Procedure for A V
V/09 Condition Types: Account Determin.
V/10 Account Determination: Access Seqnc
V/11 Conditions: Account Determin.Proced.
V/12 Account Determination: Create Table
V/13 Account Determination: Change Table
V/14 Account Determination: Display Table

BOM
CS00 BOM Menu
CS01 Create Material BOM
CS02 Change Material BOM
CS03 Display Material BOM
CS05 Change Material BOM Group
CS06 Display Material BOM Group
CS07 Allocate Material BOM to Plant
CS08 Change Material BOM - Plant Alloc.
CS09 Display Allocations to Plant
CS11 Display BOM Level by Level
CS12 Multilevel BOM
CS13 Summarized BOM
CS14 BOM Comparison
CS15 Single-Level Where-Used List
CS20 Mass Change: Initial Screen
CS21 Mass Material Change: Initial Screen
CS22 Mass Document Change: Initial Screen
CS23 Mass Class Change: Initial Screen
CS25 Archiving for BOMs
CS26 BOM deletion
CS27 Retrieval of BOMs
CS28 Archiving for BOMs
CS31 Create class BOM
CS32 Change class BOM
CS33 Display class BOM
CS40 Create Link to Configurable Material
CS41 Change Material Config. Allocation
CS42 Display Material Config. Assignment
CS51 Create standard BOM
CS52 Change standard BOM
CS53 Display standard BOM
CS61 Create Order BOM
CS62 Change Order BOM
CS63 Display Order BOM
CS71 Create WBS BOM
CS72 Change WBS BOM
CS73 Display WBS BOM
CS74 Create multi-level WBS BOM
CS75 Change multi-level WBS BOM
CS76 Display multi-level WBS BOM
CS80 Change Documents for Material BOM
CS81 Change Documents for Standard BOM
CS82 Change documents for sales order BOM
CS83 Change documents for WBS BOM
CS84 Change documents for class BOM
CS90 Material BOM Number Ranges
CS91 Number Ranges for Standard BOMs
CS92 Number Ranges for Sales Order BOMs

SAP :Build a Form with SMART FORMS

2008-03-07T13:48:00.002+07:00

SAP :Build a Form with SMART FORMS

Call the transaction SMARTFORMS.
Enter a name of a new Form to be built with SMARTFORMS and press the Create command button.

The Form Builder appears on the screen.
Any node can be selected or expanded from the left hand side tree menu.

Select the Form Interface node and provide the names of the internal tables containing the data. (In this example we have a Customer table and a Customer's Transaction Table connected with an one to many relationship).

Select the Global Definitions and provide the names of two variables for controlling the page break after finishing a section of a Customer.

In the initialization tab of the Global Definitions node, give the code calculating the number of Customers. Input and output parameters should be provided so that the code works correctly.

After expanding the %PAGE1 node, we can notice that a Main Window exists. From the context menu (appearing by clicking the right mouse button) of the Main window select Create -> Complex Section.

This Section has data which are processed repeatedly and the Output Type (the format) is Unstructured.

The data of this Section are retrieved from the internal table I_ZCUST and are stored in the data structure I_ZCUST in each iteration

At this point select the context menu of the Section and create a Text Element.

Type the names of the fields of the internal table in the General Attributes tab. The field names are enclosed in ampersands.

From the context menu of the Text Element create a series of Program lines.

This series of Program lines, (actually a single Program line), increases the index of Customers printed by one (Variable INDEX_CUST_PRN). Input and Output parameters should be declared on the appropriate fields of the tab (In this case the Input and the Output parameter is the variable INDEX_CUST_PRN).

From the context menu of the Program Lines create a second Complex Section

This Section has data which are processed repeatedly.

The Output Type (format) is a table.

Specify a Table Width and a Line Type.

Select the Data tab and specify the Loop in the I_ZTRANSACTIONS table and the Where condition.

On the Events tab select the Header and Footer events and specify a Height of the Footer.

Select the Header node and check the New Line checkbox

At this point from the %Section2 context menu select Create -> Text

On the Global Attributes tab of the Text Element type the fields of the internal table we wish to show on the form enclosed in ampersands. The Text node is Appended directly (check the relevant radio button).

From the context menu of the Footer Event select Create -> Command .

Drag the %Command1 created and drop it on the %Section2 node.

A popup window appears and select After the node %Section2.

So the %Command1 is aligned to the Footer of %Section2.
Check the Go to New Page checkbox

Select the Conditions tab of the Command element an set the condition that a new page is created if the last customer is not reached by the printing process (I e the Index of the Customers printed is less than the Number of Customers).

Start another session and call the transaction SE78

Expand the Graphics node on the left hand side tree menu, select BMAP Grid screens node and double click on it. On the right hand side provide the SAP name of a new graphic and check the Color radio button. Press the Import command button

On the appearing popup window provide the path where the bitmap image is stored and check the checkbox stating that Resides in the Printer Memory.

Press the Continue command button

The appearing screen shows that the graphic has been successfully imported into the SAP graphics management.

On the General Attributes tab of the %Graphic1 created type the SAP Name of the graphic and provide the Object, ID, Color attribute and Resolution.

Activate the Form from the menu path Form -> Activate

The function module SSF_FUNCTION_MODULE_NAME has as its import parameter a name of a Form created with SMARTFORMS and gives as output a function module name. The latter when executed with table parameters the internal tables of the SMARTFORMS Form, gives the final printout

Further reading in the SAP Library on link http://help.sap.com/saphelp_46c/helpdata/en/a9/de6838abce021ae10000009b38f842/frameset.htm. Or through the path Basis Components -> Basis Services / Communication Interfaces (BC-SRV) -> SAP Smart Forms (BC-SRV-SCR) .

by Stefanos Moschidis

SAP SPRO Chart of Accounts & Company Code

2008-02-21T21:59:00.003+07:00

SAP SPRO Chart of Accounts & Company Code

Though you can have multiple Charts of Accounts in SAP,
company codes are assigned to only one chart of accounts.
This is done in configuration (SPRO)
(T-code: OB62 - Assign Company Code -> Chart of Accounts).

T-code: F.10 - Chart of Accounts
Report of accounts in a chart of accounts.
Lots of ways to limit your results, but can’t limit by Company Code!
You will definitely want to limit by chart of accounts.

T-code: OB62 - Assign Company Code -> Chart of Accounts

T-code: OBY2 - Copy Company Code: G/L Accounts
When creating a new Company Code, just assigning it to a
chart of accounts in OB62 doesn’t automatically create those
accounts for the new company code.

i.e. you won’t be able to post any entries until you’ve created the
accounts for the company code.

OBY2 lets you copy all of the accounts that were created for
another company code to your new one.

GL Postings are assigned to only 1 company code
You can do “cross-company code” postings
(i.e. DR CoCde A and CR CoCde B), but SAP will automatically
generate the off-setting entries within each company code so
that their books stay in balance (debits = credits).

There is config around Intra-company postings to determine
where you want those offsets to go.

T-code: FS00 - Edit G/L Account Centrally
This is usually the preferred t-code for manually creating GL
Accounts since it allows you to create both the chart of accounts
piece and the company code pieces.

In FS00, you may need to create an account for multiple company
codes. This can be done by changing the CoCde and using the
“Create with reference button” in FS00.

T-code: FSS0 - Edit Accounts in Company Code
FSS0 allows you to edit just the Company Code (CoCde) portion
of the GL Account.

T-code: FSP0 - Edit Account in Chart of Accounts
FSP0 allows you to edit just the Chart of Accounts portion of the
GL Account.

T-code: CX16
Consolidation Chart of Accounts - Hierarchy Display
CX16 allows you to create/edit financial statement items
(FS Items) and their hierarchy for the Consolidated Chart of
Accounts used in the EC-CS consolidation system.

SAP Multiple Selection

2008-02-21T20:39:00.004+07:00

Pasting in multiple selections .
There are many multiple selections across SAP Screen Display.

Example :
1.Go to Tcodes FS10N
The below screen will be displayed.

2. Click Multiple Selection button

3 The below screen will be displayed.

Enter Multiple Codes you want to include in a
subscreen
Enter a Range of Multiple codes you want
to include in a subscreen.
Enter Multiple Codes you want to Exclude from a
subscreen
Enter a Range of Multiple codes you want
to exclude from a subscreen.

You can copy and paste mulitple items into those boxes (about 8 boxes) using Ctrl-V like normal.
More boxes will appear after you hit enter, and you can scroll and paste into them as well.

But if you want to paste in lots of selections at the same time, you can use the magical “Import from text file”button
The following screen will appeared

To use the Import from text file button, you can either put the content you want to add into a text file and upload it,
or you can copy it from it’s source (SAP, Excel, etc) and then click the Upload from clipboard button.
This can paste lots and lots of items to you multi-select

Also check out the Multiple Selection button .
This brings up a search screen that you can do a search and then use check boxes to select mulitple items from the search result

SAP Podcast :Report Financial Statement

2008-02-08T19:47:00.000+07:00

SAP Podcast : Make Report of Financial Statement

Hi...this podcast is under developing, i try my very first video podcast but not perfectly done yet.

SAP F.81 Reverse Accrual Defferal Doc

2008-02-08T02:37:00.004+07:00

SAP F.81 Reverse Accrual Defferal Document

Previous month you have entered accrual entries using SAP T_code : FBS1

To reverse the accrual documents do the following :

1. Go to T_code : F.81.

or from Menu path : Accounting ->Financial Accounting -> General Ledger -> Periodic Posting -> Closing -> Valuate.

2. Enter relevant field.
-Posting date & Entry date is original accrual date.

3. Tick "test run"
4. Select "Do not process"
5. Execute

6. After checking, Click "Reverse Document" button.
Back

SAP LSMW Concept

2008-02-07T23:03:00.002+07:00

CONCEPT OF SAP LSMW

LSMW read documents and convert the contents to the target structure and the corresponding fields.
Then the data from the target structure create a SAP format of the document, this document can be used to transmit data.
SAP did not provide any standards conversion.

Steps:
- Read file (local or server, and we need to accept pre-defined data source structure).

- Save the contents of the documents as LSMW documents.

- Define the relationship between the structures and fields distribution .
(as defined in the source and target structure mapping).

- Define source fields and the value of the target fields conversion rule
(LSMW file how to change the definition of target structure)

The above structure and the conversion rule defined are executable in ABAP procedures and generating SAP format documents in the transfer process or LSMW in implementation.

LSMW support of the transfer methods:
- Standard transfer process (batch input, call transaction, direct input).
- IDocs
- BAPI
- Recording SHDB and generate batch input.

STEPS :
1. Go to LSMW
Maintain object attribution

2. Maintaining the original format
- Maintain source Structure
- Maintain source fields

3. Maintaining the original format and objectives of the mapping relationship between format
4. Maintain structure relations.
5. Maintain field mapping and conversion rules.
6. Maintain fixed values, translations, user-defined routines

Achieve the original data -> objective data format
7. Specify files
8. Assign files
9. Read data
10. Display read data
11. Convert data
12. Display converted data

Upload the target format data to SAP
13. Create batch input session
14. Run batch input session

SAP LSMW Data migration for Create Vendor (XK01)

2008-02-07T22:34:00.002+07:00

SAP LSMW for data migration for XK01 transaction.
You can create lsmw for data migration as follows (using session method):
Example for xk01 (create vendor)

Initially there will be 20 steps but after processing 1 step it will reduced to 14 for session method.
1. TCode : LSMW.

2. Enter Project name, sub project name and object name.
Execute.

3. Maintain object attributes.
Execute
select Batch Input recording
goto->Recording overview
create
recording name.
enter transaction code.
start recording
do recording as per ur choice.
save + back.
enter recording name in lsmw screen.
save + back

Now there will be 14 steps.
2. MAINTAIN SOURCE STRUCTURES.
Here you have to enter the name of internal table.
display change
create
save + back

3. MAINTAIN SOURCE FIELDS.
display change
select structure
source_fields->copy fields.
a dialogue window will come .
select -> from data file
apply source fields
enter No. of fields
length of fields
attach file
save + back

4. MAINTAIN STRUCTURE RELATIONS
display change
save + back

5. MAINTAN FIELD MAPPING & CONVERSION RULE
display change
click on source field, select exact field from structue and enter
repeat these steps for all fields.
save+back

6. MAINTAIN FIXED VALUES, TRANSACTION, USER DEFINED
execute
save + back

7. SPECIFY FILES.
display change
click on legacy data
attah flat file
give description
select tabulatore
enter
save + back

8. ASSIGN FILE
execute
display change
save + back

9. IMPORT DATA.
execute
display change
save + back

10. DISPLAY IMPORTED DATA
enter ok, it willl show records only.
back

11. CONVERT DATA
execute
display change
save + back

12. DISPLAY CONVERTED DATA
execute
display change
save + back

13. CREATE BATCH INPUT SESSION
tick keep batch input folder
F8
back

14. RUN BATCH INPUT SESSION.
sm35 will come
Object name will be shown here
select object & process

SAP SD relationship tables of SO, Delivery & Invoice

2008-02-07T12:29:00.003+07:00

SAP SD Relationship between sales order number, delivery number and billing number tables

VBELN is the field name in the tables of VBAK (sales order), LIKP (delivery) and VBRK (billing).
VBFA table provides links between preceeding (sales document) and subsequent (delivery) documents.
in VBFA table a delivery can be a preceeding document to an invoice(subsequent document)

Document number can be found within the transaction table.
in the delivery : field VGBEL contain the sales order number.
in the invoice : field VGBEL contain the delivery number & field VBELV contain sales order number.

SAP Setting date format

2008-02-07T10:30:00.003+07:00

SAP Setting date format

1. Go to T_code : SU3
Or below menu path

2. Select suitable default "date format".

Back

SAP Enter Currency Exchange Rates Table

2008-02-06T00:39:00.005+07:00

SAP Change Foreign Currency Exchange Rate Table

1. Path : Accounting -> Financial Accounting -> Accounts Payable -> Environment -> Current Settings -> Enter Exchange Rates

2. Below pop-up box will be appeared.
3. Click "OK" icon

4. Below table will be displayed.
5. Click "position" button to enter selection criteria for exchange rate search.

6. Input fields in below pop-up Currency Selection criteria
- "M" is standard translation at average rate which is used in all standard foreign exchange transaction.

7. Click "OK" button.

8. Below currency exchange rates table will be displayed.

9. Click "New Entries" Button for enter a new exchange rate.

10. Enter the fields in below table
-ExRt = Exchange rate type
-ValidFrom = Effective date of the exchange rate displayed.
-Ratio(from) = always 1 (default)
-From = Originating currency for the transaction (e.g. USD)
-Dirquot = Direct Quotation e.g. 1 USD = JPY.114.06
-Indir.quot = Indirect Quotation e.g 1 JPY = USD. 0.0088
This field is not in use and always display "0.00000"
-To = always 1 (default) this is reporting currency (e.g. JPY)

Setting Option

SAP SD Configuration

2008-02-05T02:15:00.001+07:00

SAP SD Configuration

1. Maintaining Sales Organization
Sales Organization is an organizational unit responsible for the sale of certain products or services.
IMG -> Enterprise Structure -> Definition -> Sales and Distribution -> Define, copy, delete, check Sales organization

2. Assigning Sales Organization to Company Code
This assignment ensures all the sales made through this Sales Organization are accounted for in the assigned Company Code (Company Code is created by FI Consultant)
IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign Sales Organziation to Company Code .

3. Maintaining Distribution Channel
Distribution Channel is the way, in which Products or Services reach Customers.
IMG -> Enterprise Structure -> Definition -> Sales and Distribution -> Define, copy, delete, check distribution channel

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

5. Maintaining DivisionDivision
is a way of grouping materials, products, or services.
IMG -> Enterprise Structure -> Definition -> Logistics - General -> Define, copy, delete, check division

6. Assigning Division to Sales Organization
IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign division to sales organization

7. Setting up Sales Area
All the sales are made from a particular sales Area.
For creating a Sales Order Sales Area is compulsory.
IMG ->Enterprise Structure -> Assignment -> Sales and Distribution -> Set up sales area

8. Assigning Sales Organization- Distribution Channel- Plant
Plant is created by MM Consultant.
IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign sales organization - distribution channel - plant

9. Define Shipping Points
Shipping Point is the Organizational element, which is responsible for shipping the Materials to the Customers.
IMG -> Enterprise Structure -> Definition -> Logistics Execution -> Define, copy, delete, check shipping point

10 Assigning Shipping Point to Plant
This assignment ensures that goods from different Plant can be dispatched from different Shipping Points.
IMG -> Enterprise Structure -> Assignment -> Logistics Execution -> Assign shipping point to plantNote: Ensure to do the undermentioned configuration also though it is not in Customizing node of Enterprise Structure.

11. Defining Common Distribution Channels for Master DataUse
The purpose of this activity is to define distribution channels which have common master data.
Procedure Access the activity using one of the following navigation options:
IMG Menu -> Sales and Distribution -> Master Data -> Define Common Distribution ChannelsTransaction Code: VOR1

12. Defining Common Divisions for Master DataUse
The purpose of this activity is to define distribution channels which have common master data.. Procedure Access the activity using one of the following navigation options:
IMG Menu -> Sales and Distribution -> Master Data -> Define Common DivisionTransaction Code: VOR2

SAP MIGO Partial Goods Receipt of a PO

2008-02-03T22:13:00.002+07:00

SAP MIGO Partial Goods Receipt of a PO

1. Go to T_code : MIGO

2. Select Goods Receipt
3. Select Purchase Order
4. Enter PO number for goods to be received.
5. Hit "Enter"

6. Enter Document date & posting date
7. Enter Header text (comment) if necessary.
8. Close detail data.

9. Notice that movement data is "101"
10. If you only received first item, then Check the "OK" box for first line item.

therefore, the second item need not be processed

10. If you only received 3 pcs out of 10 pcs of item one & 2 pcs out of 10 pcs of item two, then Check the "OK" box for both line item

11. Input actual quantity (3 & 2 pcs ).

12. Hit "Enter"

11. Click "Check" button to find out if there is any error.

12. Check the "status" column .

. Green means OK

. Yellow means Warning

. Red means error

13. This is just a warning that there are still quantities yet to be processed in this PO.

14. Click the "check mark"

SAP MIGO Goods Receipt all items in a PO

2008-02-03T17:55:00.002+07:00

SAP MIGO Goods Receipt all items in a PO.

1. Go to T_code : MIGO

2. Select Goods Receipt
3. Select Purchase Order
4. Enter PO number for goods to be received.
5. Hit "Enter"

6. Enter Document date & posting date
7. Enter Header text (comment) if necessary.
8. Close detail data.

9. Notice that movement data is "101"
10. Check the "OK" box.

11. Click "Check" button to find out if there is any error.
12. Check the "status" column .
. Green means OK
. Yellow means Warning
. Red means error

13. Post, If the message is "Document is OK"

14. Noted the document number.

SAP Create SO in HQ (Supplier) from subsidiary PO data

2008-02-03T17:16:00.001+07:00

SAP Create SO in HQ (Supplier) from subsidiary (Buyer) PO data

Normally used for intercompany transaction.

If Subsidiary A raise PO with pricing to HQ.
It doesn't have to be a special pricing procedure.
You can choose the following :
- 1-step move with no billing/delivery (intercompany 301),
- 2-step move with no billing/delivery (intercompany 351),
- 2-step move with delivery,
- 2-step move with delivery and billing

You may configure where buyer (normally subsidiaries in the same group) can create Sales Order in supplier (normally Head Quarter).

These are all standard out of the box, and data flows naturally from document to document.
The invoice can cause the invoice receipt to be automated, but it relies on a little EDI setup.

If Buyer A raise a PO on HQ and HQ raise Delivery against the buyer PO.
You can dictate in the billing create from delivery that the price be adopted from originating PO.

Ensure that you have a price condition in SD that matches the name of the price condition used in the PO, then in VTFL at item level, set Pricing Souce B - Purchase Order/Delivery.

This set-up can reduce a workload to issue SO one by one in HQ which has many subsidiaries raise PO on HQ.

Subsidiary must have a authorized person to approve PO which will create SO in HQ.

Each subsidiary will be given a different Tcode
e.g : Subsidiary A :ZPT114R010, Subsidiary B :ZPT114R011
The sample below is not standard SAP.

1. Below is the sample after a subsidiary enter the Tcode ZPT114R010

2. Please enter some search conditions.
If you don’t enter search condition, the procedure will be very slow.
I recommend you to enter search conditions as many as possible.

3. Click the “Execute” icon.

4. The POs only such that the Document type of which is ZOC and the vendor of which is Head Quarter are displayed.

Approve the lines whose statuses are Red Signal.
Please select the line which you want to approve.

■■■In case that there are plural line items for single PO, each line item is displayed.
Select all line items which have the same PO number and approve them. ■■■

5. Click “Approve” icon.

6. Please check the message and the statuses of the lines.

The status will be Green after approving

7. You can check the status of approving at the right of this screen.
There is information : Approved by, approved date & time, etc

SAP ME2L Overview Pending PO

2008-02-03T16:26:00.001+07:00

SAP ME2L Overview Pending PO

1. Go to Tcode ME2L

2. Click "get variant" icon

3. Select variant which you have been saved.

4. Click "OK" icon

5. The below screen will be appeared

6. Enter purchasing organization

7. Enter purchasing group

8. Enter Plant

9. List of Pending PO will be displayed.

SAP ME22N Change Purchase Order

2008-02-03T03:00:00.001+07:00

SAP ME22N Change Purchase Order

1. Go to Tcode ME22N

2. Make sure that Goods Received & Invoice Verification were already reverse.

3. Highlight all line items and click "trash" icon

4. Click "Yes" to the warning.

5. Save

6. Notice the message

7. By pass the warning message by hitting enter.

8. Noted the document number.

SAP MIGO Adjustment of Physical Inventory Difference

2008-02-02T21:36:00.001+07:00

SAP MIGO Adjustment of Physical Inventory Difference

Case :
Company physical inventory has different quantity with SAP Inventory quantity.
The physical inventory is 2 units more than book keeping.

※In this Scenario, the quantity is increased.
For decreasing (GI), be sure of using the other Mvt. Type.

Mvt Type 701 : Increasing (GR Phys. Inventory)
702 : Decreasing (GI Phys. Inventory)

1. Go to Tcode : MIGO

2. Select "Goods Receipt"
3. Select "Others"
4. Select Movement type "701".
5. Click "Material" tab
6. Enter Material Code

7. Click "Quantity" tab
8. Enter quantity to increase.

9. Click "Where" tab
10. Enter plant & storage
11. Make sure movement type is correct.

12. If this screen is appeared, please hit “Enter” key to extinguish this screen.

13. Click "Check" icon.
14. Post if the message is "Document is OK"

Back

SAP MIGO reduce inventory for obsolete material

2008-02-02T17:20:00.001+07:00

SAP MIGO Reduce Inventory for disposal, obsolete, internal and other usage material except sales

1. Go to Tcode MIGO

2. Select "Goods Issue"
3. Select "Others"
4. Enter date
5. Select moving type : "551"
6. Click "material" tab
7. Enter material code

8. Click "Quantity" tab
9. Enter quantity of inventory you want to reduce

10. Select "where" tab.
11. Enter plant and storage
12. Check movement type.

13. Select "Account Assignment" button.
14. Enter suitable G/L account code
e.g. obsolete material account code.
Default account code will be used if we do not enter in this field.
15. Enter "cost center".

16. Click "check" button.

17. SAVE, If "the document is OK" message displayed.

18. Noted the document no.

Back

SAP ME21N Create Purchase Order

2008-01-30T01:28:00.001+07:00

SAP ME21N CREATE PURCHASE ORDER

Go to T.code ME21N

1. Choose Order type

2. Enter Vendor

3. Enter Document Date

4. Enter Organization group

5. Enter Material code
Note : you can overwrite material description if necessary

6. Enter P.O. Quantity

7. Enter Net Price

8. Delivery date by default is the same with document date

Enter Delivery date if necessary

9. Enter Plant

Hit "Enter" button

10. Enter storage date

11. You may add line item as neccessary

12. At this point showing line item detail 10's information.

13. To check Net Price go to "condition" tab

Notice the relation of the price

14. Add comment at the header "texts" tab if neccesary

15. Click "check" icon to see whether there are errors/warnings.

Note that document with error cannot be saved.

16. Note the saved document number.

Use Tcode ME23N to view this document

SAP ME23N Display Purchase Order

2008-01-30T00:41:00.001+07:00

SAP ME23N TO VIEW PURCHASE ORDER

A Purchase Order document is divided into 3 sections:

1. Header
Contains information of the document as a whole
*This section includes the document currency and Net price info

2. Item Overview
Contains a summarized information of all items (materials)

3. Item Detail
Contains a detailed information of each item (material)
*This section includes each item price and history (if applicable)

Click the icon to expand or collapse

Back

SAP MMBE Stock Overview

2008-01-29T23:57:00.002+07:00

SAP MMBE Stock Overview

1. Go to T.code MMBE

2. Enter Material Code and execute

3. The amount & location of the material will be shown.

4. If No data is shown , probably the material master code has not related to your company.

5. If the following message is shown, means you entered a wrong material code or this material code has not been created.

Back

SAP Cost Centers

2007-12-12T00:07:00.003+07:00

SAP Cost centers

Cost centers are used to track where cost occur in the organization.
As costs are incurred, they are assigned or posted to the appropriate cost center.
The posting and assignment of costs to cost centers is a critical step in using the CO module.

Cost centers are organized in a Standard Hierarchy.
The Cost Center Standard Hierarchy is used to structure the cost centers in an organization.
All cost centers must be entered in the Standard Hierarchy.

To display the standard hierarchy follow the menu path:
Accounting ->Controlling ->Cost Center Accounting ->Master data ->Standard Hierarchy ->Display

Then enter the controlling area code and hit "enter" button.

The following screen will be appeared

Simple example of cost centers is distribution of rental fee to several cost centers in G/L

Back