SAP FUNCTIONAL

SAP EWM Useful Links

2013-03-11T16:20:00.000+05:30

SAP-RFID Integration Link for book

SAP EWM Implementation Guide

SAP CIF Interface

Stock Transfer Order by SD route

2012-06-13T18:56:00.002+05:30

In a company, goods movements do not only occur in the form of goods receipts and goods issues. Depending on the organization of the company (for example, decentralized storage) and its sales policy, internal stock transfers might also be necessary.

Stock transfers can occur at three different levels:

1) ST for Cross Company Plants

If the plants involved belong to different company codes, the transfer between plants is also a transfer between company codes. In this case, the system creates two accounting documents when the goods issue is posted. The stock posting is offset against a company code clearing account.

2) ST from plant to plant within same company code

A stock transfer from plant to plant not only leads to a change in stock quantity in both plants; if both plants are assigned to different valuation areas, an accounting document is also created.

3) From storage location to storage location (in the plant)

A stock transfer from storage location to storage location in the same plant simply causes an update of the stock quantities in both storage locations. It is not relevant for accounting.

One-Step Procedure
One material documents prepared.
Mat. Doc 1: Two line item
                  One for removal from storage location at the supplying plant.
                  One for putting into storage location at the receiving plant.

Two-Step Procedure
Two material documents prepared.
Mat. Doc 1: Two line item
                  One for removal from storage location at supplying plant.
                  One for putting into stock in transfer at receiving plant
Mat. Doc 2: One line item
                  For stock in transfer at receiving plant into storage location at receiving plant.

Configuration of Plant to Plant STO & Return STO:

Useful links from Help.sap.com

2012-04-17T12:33:00.000+05:30

SAP SD (Sales and Distribution)
Help.sap.com for SAP SD

SAP EWM (Extended Warehouse Management)
Help.sap.com for SAP EWM

Sales SD-SLS
Special Business Processes for Sales
Help.sap.com for SAP SD-SLS

ABAP Programming on SAP NetWeaver

2011-11-03T13:01:00.000+05:30

ABAP Programming

Programming of application programs on the SAP NetWeaver Application Server ABAP.

SAP SD Training

2011-08-11T14:28:00.002+05:30

http://www.magnatraining.com/sap-sd-training/

Sap SD Pricing Fundamentals

2011-08-10T16:15:00.001+05:30

SAP SD Pricing Fundamentals

E1 Sales procedure

2011-08-03T12:36:00.010+05:30

E-1, E-2 are the names of the forms issued for declaring that the goods are sold/purchased in transit.

E-1 sales.:
In this 3 states/ parties are involved during the transportation of goods. And as per the state tax laws, upon entering each state, a central tax of 4% for each is state is payable. However if the goods are redirected or endorsed to a different party then to avoid multiple taxation, this sale in transit is applied.

i. e.

Customer/Purchaser: Mr. A at MP

Trader/Dealer: Mr. B at Gujarat

Manufacturer: Mr. C at Maharashtra

A Customer/Purchaser Mr. A (MP) want to buy some products from Mr. B (GJ) which is product expert. But B hasn’t stock with him so he will contact his friend Mr. C (MAH) which is a manufacturer.

Now, Mr. B will ask Mr C to sell it to him, but deliver it to Mr A.

Invoice:

Mr. C to Mr. B (Mr. B as buyer and Mr. A as consignee) with 4% CST for MP-MAH.

The products will go directly to Mr A (MP).

Mr. B (GJ) also raise invoice to Mr. A. (w/o Sales tax, with its profit, final payment)

So, CST is already applied to inv from Mr. C to Mr. A for actual good delivery, Mr. A do not required to pay additional sales tax for inv from Mr. B. This will save tax to Mr. A of MP from being taxed at GJ.

Forms involved:

Mr. A will issue a C form to Mr B.

Mr. B will issue a C form to Mr. C.

Mr. C will issue an E-1 form to Mr. B

And if above sequence is broken at any point the party liable (Mr. A) shall have to pay 10% as CST.

In this case Form E-1 is for claiming exemption from CST on subsequent sale. So, that Mr. B can raise invoice w/o sales tax.

E1 Yahoo Answers

SAP SD common errors while configuration

2011-06-06T20:25:00.003+05:30

1. "Define <DH16/B1/CP> first as a general sales area!"

Have created Sales Area and new Sales Document types.
IN IMG have set up sales area[example DH16/B1/CP]. While assigning the Sales area to Sales Document types system is giving the following error message even after setting up the Sales area.

error message:

"Define <DH16/B1/CP> first as a general sales area!"
Message no. V2127

Diagnosis
You want to define allowed sales document types for a sales area which is not maintained as a common sales area. This is a sequence infringement of Customizing activities.
System Response
The entry is not allowed.

Procedure
First, maintain the sales area <DH16/B1/CP> as a common sales area, and then assign allowed sales document types. This means: Complete the IMG activity Assign sales area to sales document types in the sequence entered here."

Solution:

Kindly refer Common Distribution Channel/Sales Organization and divisions before you proceed.

2. "Please enter Business Place in line 000".

Have created Plant(WP01), Error comes while releasing accounting document.

error message:

"Please enter Business Place in line 000".

Procedure:

SPRO | Cross-Application Components | General Application Functions | Business Place

Assign Business Place to Plants: WP01 --> INGB

INGB is Business Place according to your plant location (India Gujarat Baroda)

3. "Balancing field "Business Area" in line item 002 not filled"

Have created Plant(WP01), Error comes while releasing accounting document.

error message:

"Balancing field "Business Area" in line item 002 not filled"
Message no. GLT2201

Procedure:

First check Business Area in Sales Document. Item --> Account Assignment. If it comes then no problem.

Otherwise following config need to be maintain.

You can assign BA to

1) Plant/Dvision
Enterprise Structure | Assignment | Logistics - General | Assign Business Area to Plant/Valuation Area and Division

or

Enterprise Structure | Assignment | Sales and Distribution | Business Area Account Assignment | Assign Business Area To Plant And Division

2) To Sales Area
Enterprise Structure | Assignment | Sales and Distribution | Business Area Account Assignment | Assign Business Area by Sales Area

Once this config is maintain, we need to define rule for selecting BA in Sales Order

Enterprise Structure | Assignment | Sales and Distribution | Business Area Account Assignment | Define Rules By Sales Area

i.e. Either from Plant/Division or Sales Area

4. Please maintain sales org./division/distr. channel in supplying plant XYZW

Please maintain sales org./division/distr. channel in supplying plant XYZW

Message no. 06846

Procedure: In the case of a stock transfer with a delivery and a billing document the Sales and Distribution (SD) data sales organization, distribution channel, and division must be maintained for the supplying plant so that the shipping index can be updated.

Materials Management | Purchasing | Scheduling Agreement | Set up Stock Transport Scheduling Agreement | Define Shipping Data for Plants

It will update T001W table.

Generally only Sales Area required for supplying plant to create STO.

Other are common as per standard configuration for STO.

If above config is missing then although all shipping point relevant setting inline it will give you following error:
"Not possible to determine shipping data for material ABC"
Message no. 06280

SD Documents number Ranges (VN01)

2011-04-19T20:36:00.000+05:30

Object for SD document's number Range: "RV_BELEG"

T-Code: VN01

It depends on Number Range key’s Ext indicator.

1. Internal

2. External (if ticked)

Various No range Keys are:

OR -Order

LF -Delivery

R2 -Billing

To maintain it click on the "Interval" button and enter No Key, From to To number, maintain Ext indicator.

Customer No Range

2011-04-06T18:22:00.000+05:30

Customer Account Group:

No range assignment per account group

- It depends on Number Range key’s Ext indicator.

Internal
External

- Assign Number Range Key to Account Group.

Number range object's characteristics

2011-04-06T18:09:00.000+05:30

RV_BELEG – No range object

To year Flag - Tick when Fiscal year base.
No interval Rolling – Tick then prevents no. range object interval from automatically starting from beginning at upper limit.
No range Transaction - For maintaining no. range (must be unused).
Warning – Warning for Percentage of numbers remaining in a number range.
Buffering or not.

Reconciliation Account

2011-03-11T10:02:00.001+05:30

Most SAP people might be asking, what is a reconciliation account and special general ledger indicator in SAP Financial Accounting?

First, you must understand the definition of general ledger. General ledger is the main accounting record of a business which uses double-entry bookkeeping. In SAP, the central task of G/L accounting is to provide a comprehensive picture for external accounting and accounts. Transactions that have a financial impact are captured by the general ledger. The transactions could be originated from other modules. Example, posting of goods receipt (MIGO) performed by purchaing personnel (MM module) have already a financial impact. It increases the inventory balance and increases the GR/IR clearing account. The accounting journal entry the transactions MIGO create is debit (dr) Inventory account (G/L) and credit GR/IR clearing accounts (G/L).

The general ledgers summarize all financial transactions of a Company. It is the the basis of the preparation of the Company’s Financial Statements.

Now, let’s dig it further. Reconciliation Accounts are G/L accounts that receive postings from a subsidiary ledgers. Meaning, transactions data are not posted directly to recon accounts. Example of recon accounts are Accounts Receivable, Accounts Payable and Fixed Assets G/L. For accounts receivable G/L the subsidiary ledger is the customer account. All transactions with the customers are posted directly to the customer account and the recon account is automatically updated. How this thing happen? Well, when you create a customer account you specify under the Company Code data the reconciliation account.

So, all normal transactions to the customer e.g. sale of goods are posted to the recon account defined in the customer master data. Next question would be, what G/Laccount should be updated for postings of customer down payment (advance collection)? For proper accounting, downpayment should not be posted to Accounts Receivable – trade. It should be posted to different G/L account e.g. Advances from customer. Well, how would the said transaction be posted to Advances accounts.

Reconciliation Account in General Ledger

The reconciliation account in G/L accounting is the account which is updated parallel to the sub ledger account for normal postings (for example, invoice or payment).

For special postings (for example, down payment or bill of exchange), this account is replaced by another account (for example, 'down payments received' instead of 'receivables').

The replacement takes place due to the special G/L indicator which you must specify for these types of postings.

What's need of such Reconciliation Account?

Well, with reconciliation accounts, one can generate a balance sheet or profit and loss account at any time, since amounts posted in sub-ledger are also reflected in the general ledger.