Subscribe

RSS Feed (xml)

Powered By

Skin Design:
Free Blogger Skins

Powered by Blogger

 

Sunday, October 14, 2012

SAP SD relationship tables of SO, Delivery & Invoice


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 LSMW Data migration for Create Vendor (XK01)

SAP LSMW Data migration for Create Vendor (XK01)    

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 RELATIONSdisplay change
save + back
5. MAINTAN FIELD MAPPING & CONVERSION RULEdisplay 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 DEFINEDexecute
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 DATAenter ok, it willl show records only.
back

11. CONVERT DATA
execute
display change
save + back
12. DISPLAY CONVERTED DATAexecute
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

Saturday, October 13, 2012

SAP LSMW Example with Description

SAP LSMW Example with Description

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

Friday, October 12, 2012

SAP F.81 Reverse Accrual Defferal Doc


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.

Thursday, October 11, 2012

SAP SPRO Chart of Accounts & Company Code


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
SAP: OBY2
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.

Wednesday, October 10, 2012

SAP SD important transaction codes


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

PricingV/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

Tuesday, October 9, 2012

How to Copy or Upload Excel Journal Entry to SAP

Copy or Upload Excel Journal Entry to SAP

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 sheetThat 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.

Recent Topics