Showing posts with label SAP SD. Show all posts
Showing posts with label SAP SD. Show all posts

Difference between Cash Sales & Rush Order

Cash sales are order related billing whereas Rush Order is delivery related.

 

Cash sales are not relevant for availability check, as you will be picking the goods whereas Rush Order is relevant for availability check.

 

Cash sales are also not relevant for credit management whereas Rush Order is relevant credit management.

 

Cash sales uses RD03 as output, which immediately prints the invoice whereas Rush Order uses standard output RD00.

 

Cash sales have one time customer account group where as RO normally doesn't.

 

For Cash sales order type is BV or CS and for Rush Order it is RO

 

Cash sales triggers petty Cash a/c where as in Rush Order customers account is debited.

 

Delivery and settlement will be done immediately in Cash sales where as in Rush Order only delivery will be done immediately.

Difference between VF04 & VF06

VF04 is used to MAINTAIN BILLING DUE LIST based on the Delivery date as default, Means the Delivery documents which has the same date and for which the Billing has to create on a particular date uses this Transaction

 

VF06 is used to create the Billing for all the Deliveries irrespective of Date,

 

You have to give the Billing data for VF04 and it is not required for VF06 (in summary).

 

In VF06, you can also schedule the invoice printing with required date and time. Once the system date and time reaches this, it will run in background.

Difference between PICKLIST & PUTAWAY LIST

The PICKLIST is used at the time of doing PGI -outbound delivery, it helps us to identify what materials what quantity are to be picked from which storage location for purposes of executing delivery and subsequent Goods issue.

 

Whereas PUTAWAY list is being at the time of PGR- inbound delivery, goods return. This PUTAWAY list will let us know that what material, what quantity is returned with reference to which particular SO and delivery. The goods returned are isolated and put in separate storage location from your normal one and PUTAWAY helps there.

 

In short PICKLIST is for removing goods from your storage location while PUTAWAY is for placing goods back.

Difference between ECC 6.0 vs 4.7EE - SAP FI / SD / MM / ABAP (Functional & Technical)

ECC means Enterprise Central component.


SAP R/3 4.7 is based on the 3-tier architecture. SAP is continuously upgrading the software, which is called as release versions for example SAP R/3 4.6C, SAP 4.7....

 

Now SAP evolved into using the Internet technology and is called as service oriented architecture (SOA). There are lots of functionalities available in ECC 5.0 and ECC 6.0 compared to R/3 in integrating with other systems. Probably to understand the specific release dependent changes, you can go thro the help documentation. For example to understand the diff between ECC 6.0 and ECC 5.0 please go thro the link:

 

Release Notes for SAP ERP Central Component (English) – Click here

 

Some of the differences in SD Module are:


1. Document Flow


In ECC 6.0, the flow of sales documents is seen much better and improved as compared to 4.6C. Once you look at the screen, you will clearly figure out the difference.

2. Sales Order Look and Feel


There are more tabs in ECC 6.0 for Item Level Details.
The Sales Doc. appears as supremely perfect.

3. ECC 6.0 is built on Net Weaver Technology (that possess SOA i.e. service oriented architecture), Hence more reliable and improved as compared to previous one.

Release Notes for SAP ERP Central Component (English) – Click here

 

Some of the differences ABAP Module side:

 

  1. For installing ECC 6.0 you required a solution manager key. With out solution manager key you cannot install ECC6.0.
  2. ECC 6.0 is called net weaver component here you have ABAP+JAVA stack & for installing 4.6 you don't require solution manager key. It only having ABAP stack.
  3. ECC6.0 supports UNCODE & 4.6C supports NONUNICODE.
  4. Major difference is ECC6 is net weaver product having WASJAVA+ABAP - secondly support Unicode apart from this we have other diff. you can get from master guide from service.sap.com/instguides.

5.      In terms of ABAP some function modules are obsolete in 4.7. e.g. WS_UPLOAD, WS_DOWNLOAD etc. You can find the list of obsolete FMs in the table RODIR. These need to be replaced in the ECC System.

6.      Also ECC is very strict in case of EPC Errors. You need to check the EPC and remove the call function interface errors where it says SLIN observes catching of a runtime error. These might work with no issues in 4.7 but will short dump in ECC.

7.      If you are doing to a Unicode conversion also. You need to check the transaction UCCHECK for Unicode errors. You also need to replace obsolete statements like >< and => , =< etc.

8.      If you want to know more ABAP changes go to transaction ABAPDOCU and there is a node ABAP Changes by Release. You can see more ABAP Changes version by version here.

9.      ECC is more towards OOPS concepts, ECC is very developer friendly

10.   It has new debugger.

11.   New Enhancement Framework is introduced in ECC.

12.   It is more efficient to use Adobe forms in ECC.

13.   5.0 ECC - Build in Net Weaver Platform & 6.0 ECC - Build in Net Weaver Platform with Solution Manager

14.   ECC has new options in BADIs where you can create your own badis and implement it.

15.   You have new concept called Implicit and explicit source code plugins in ECC.

16.   Has webdynrpo component accessible from SE80 transaction Itself.

 

Some of the differences FI Module side:

 

 

1.      ECC 6.0 enables Business area posting - Segment reporting made easy.

2.      Profit center accounting is through new GL.

3.      Document splitting: Split of entry to post assets and liabilities to respective profit centers. (Balance sheet items)

4.      Enables commitment of FM, improved CRM feature & Mobile sales feature

Here are the list of Transactions not their in ECC 6.0

QAS1 Download Insp. Specs. (Obsolete)
QAS2 Download Basic Data (Obsolete)
QAS3 Upload Results (Obsolete)
QAS4 Upload UD (Obsolete)

WLF1K Report used to generate WLF1K is: SAPLWLF1
O07C Report used to generate O07C is: SSFPSEMAINT

 

 

Check the below links to download the PDF files for the release notes of MM Module:

ECC 5.0 - MM Module Release notes

SAP R/3 MM Module Release notes

 

Some of the differences Basis/Technical Module side:

 

If you're "Basis/Technical", focusing on the underlying technical "Basis" or "NetWeaver" versions will help you stay on the right track. Technically, ECC 6.0 is 2 "technology" versions higher. Following is the terminology/version information for the last 3 ERP product versions:

SAP R/3 Enterprise (4.7x)
SAP BASIS 6.20

SAP ERP 2004
SAP NetWeaver 2004 (BASIS 6.40)
ECC 5.0

SAP ERP 2005
SAP NetWeaver 2004s (BASIS 7.00)
ECC 6.0

The main technology feature delivered with NetWeaver is the integrated J2EE engine (Web Application Server Java).

 


You can use the below link for finding the differences between the 2 versions.
http://solutionbrowser.erp.sap.fmpmedia.com/



Can find the difference in release notes of each SAP version. Here are the links.

http://help.sap.com/saphelp_47x200/helpdata/en/fc/e3003deddfae4de10000000a114084/frameset.html


http://help.sap.com/saphelp_scm50/helpdata/en/28/b34c40cc538437e10000000a155106/frameset.html


http://help.sap.com/saphelp_erp2005/helpdata/en/43/68805bb88f297ee10000000a422035/frameset.html

SAP FI / MM / SD : Tax

§ Types:
i. Tax on sales/purchases
ii. US sales tax
iii. Additional taxes (country-specific)
iv. WHT
§ With the provision for two taxation types:
i. Federal/country level - national level, with uniformly defined rates.
ii. State/jurisdiction level - rates defined by state/jurisdiction
§ In some countries taxes are even levied on both levels.
§ System supports:
i. Calculating the tax amount
ii. Posting to defined tax accounts
iii. Performing tax adjustments - for cash discounts or other form of deductions
iv. Tax reporting
§ Calculates the tax amount from:
i. Base amounts w (gross) or w/o (net) a cash discount (exp / revenue)
ii. Tax codes to check or calculate the tax amount
§ National regulation determine whether tax base amount is gross / net – you have to define which is to be used for each CC or for the highest level of the jurisdiction code.
§ Tax on sales and purchases: is the balance of the output tax and input tax
i. Output: on the net value of the goods and is billed to customer – liability of company to tax authorities
ii. Input: on the net invoice amount and billed bye vendor – receivable by company from tax authorities
iii. Tax payable: output tax (-) input tax
§ US Tax on S&P – Sales & Use tax
i. Both are different
ii. Both are apply to goods consumed by the customer
iii. Goods used in production / for resale to 3rd party remain untaxed
iv. Taxable good is sold either sales or use tax is levied – so goods taxed only once
v. Sales tax is collected by a vendor on a sale and remitted to the jurisdiction of the customer
vi. If customer are exempt – can specify in master record by entering appropriate indicator (Sales Area – Billing tab)
vii. Sales tax based on – Material & Customer location - posts in SO mgt & Purchasing mgt.
viii. Customer only has to pay use tax – if he was not charged sales tax by the vendor
ix. This may be the case if the vendor does not have a “presence” in the state of the customer or if the customer has a “self-assessment permit”
x. Customer determines the use tax amount and remits it to the jurisdiction where the goods are consumed
§ Tax Calculation Procedure:
i. Assigned to every country
ii. Contains:
1. order of steps:
2. tax types (condition types): that apply for the country – necessary for tax calculation
3. account key / transaction key: for additional specifications & automatic account determination
iii. TAXUSJ: including use of jurisdiction codes - TAXUSX: when employing an external tax package
iv. Condition types are tax calculations that are valid for the country
v. Base amount is the rev / exp item.
§ Jurisdiction Code:
i. Combination of the codes of tax authorities that tax movements of goods and use their own tax rates
ii. 4 possible levels below national level: State – Country – City or sub-city
iii. Using involves 2 steps:
1. have to define length of the individual element of the code for the format of the jurisdiction code
2. code must define on every level
iv. STATE - COUNTRY CODE - CITY CODE - DISTRICT CODE
v. When you post taxes with JC, you can enter taxes per J level / per tax level
§ Tax Code:
i. You can enter tax code when you post the document – this is the main connection – this depends on country uses as tax calculation procedure with tax jurisdiction codes or not
ii. Linked with either of the following:
1. Country key
2. Combination of country key and tax jurisdiction code
3. Tax codes within a jurisdictional taxation method are date-specific – you can choose whether the document date or posting date is valid for the tax calculation.
iii. Contains the tax rates.
iv. Tax rates assigned to tax types used in the procedure
v. A tax code may have several tax rates entered for different tax types (if line item is to be taxed with several tax types), but usually only one tax is entered.
vi. Zero tax :
1. exempt but have to reported to tax authorities – for this separate tax code is created
2. goods issue, goods movement, and so on – special tax code must be assigned to these transactions
vii. Tax type determines if the base amount is “percentage included” or “percentage separate”
viii. Check indicator: To detect the deviation between the tax calculated and the tax amount entered – either issue an error message (indicator set) or a warning message (indicator not set) - not for input tax codes because user must post the tax amount from the invoice regardless of whether it is correct or not
§ Tax Postings:
i. Separate line item to a special tax account
ii. Taxes with certain transaction/event keys are distributed to the relevant expense/revenue item (this is the case for sales tax payables or other non-deductible input taxes)
iii. For each transaction event key ( Posting key, Rules & Tax accounts)
iv. Exchange rate differences occur because of tax adjustments in foreign currencies – these are posted to normal account for ex rate differences
v. For each company code you can specify that the exchange rate for tax items can also be entered manually or is determined by the posting or the document date – the resulting differences posted to a special account
§ Tax Accounts:
i. Tax code properties determines whether or not the tax posted is I/O tax.
ii. Accounts to which tax items are posted define by entering the “Tax category” in GL:
1. “ “ - non tax-relevant postings (e.g., bank postings)
2. “-“ - postings that require an input tax code
3. “+” - postings that required an output tax code
4. “*” - postings which require any tax code
5. “xx” - predefined tax code
iii. “Post automatically only” must be selected if you don’t want to post tax manually
iv. “Posting without tax allowed”
1. can post to this GL without specifying tax code
2. necessary for tax postings within a jurisdiction code tax calculation procedure to foreign customers who do not have a jurisdiction code
v. Accounts for cash discounts need an entry in “Tax category” field if the system is supposed to post tax adjustments
§ READ 303 PAGE FOR EU RELATED TAX STUFF