To mr sadhu kishore

mr. sadhu kishore
i am not talking about delivery split or different billing
documents
i am talking only about payment transactions at item level
hi
sap gurus,
I have 4 line items for a customer in the sales order at each
item level it should carry payment transactions of that particlar
item on its own.
where we will configure in SPRO for that.
regards,
balaji.t
09990019711.

Dear Balaji,
Customer payments can be of many type:
1. Card payments - could be debit, credit etc... = for this u need settings for Web Application server and when u enter card no. then it should go and check the respective server i.e ICICI , HDFC etc to check limits and get clearance from them. Genrally this is used when we configure IS - Retail or selling via internet. In normal cases also we can use it.
2. Customer payments - via Cheqye, DD etc - We use the bussiness process flow as open items.
i.e to be very clear, it is not order which is billed but an item is billed so u maintain prices for items and when u pass bill doc to accounting u pass as items for payment. In copy controls u have allocation no. which gives to which order this item belongs to.
Now u can goto TC: F-28 and post customer payment then u balance against open items and not bill doc....
This is how we balance cust payments item wise ? and it is only item wise only we take payment in SAP.
Hope i am clear.
regards
krishna

Similar Messages

STO - ERROR IN ME21N - sadhu kishore , ayub .

HI ALL ,
WHILE trying to transfer stock between 2 plants in different copmany codes , in ME21N the system is unable to recognise the IMG config , thou all is fine .
can any one pl guide ?
pl do guide with reg to stock between 2 plants in different copmany codes .
well all is fine with stock transfer between 2 plants in one company code .
Thanks ,
jerry

In the ME21N create screen Click on ALT+F12 (Custom Local Layout) click on Option>Click on Expert in the Controls> flag the check box:
Show Keys in All Dropdown list
& Sort items by Key
Click apply and ok
regards
John

REBATE SETTLEMENT ERROR. " SADHU KISHORE , AYUB .

Hi all,
well have created material rebate in vbo1 & the rebate is for 50 .In vf02 in accounting doc the amounts are displayed as :
ERU rebate accurals : 50, & reverse for other :50 .
can u pl let me know wts the amount 50 ,which says reverse for others.
2nd part while paying partial settlemt with amount 20 ERB is posted with the amount 20 . and ERU says 20 & the same 20 is shown across reverse for others
3rd part balance 30 is settled in full but sill its open .
The final settlement amount is being doubled even its settled .
MY concern is should i do final settlement or any other procedure to settle rebates .
Regards,
jerry .

Run time error while creating Ecommerce Order

Dear Friends,
we are using ECC 6.0, Ecommerce 5.0 applications run internet sales.
After selecting the requried products from the product catalog while trying to save the order I am getting a Run time error and also my session is getting logged out of the web shop.
I have searched the threads on similar issue, but found no clue yet..
Any help is highly appreciated.
Regards
Sadhu Kishore

#1.5 #005056A31282001C0000000400001AD800047FB93365B5C7#1266333314895#/Applications/BusinessLogic#sap.com/crmentitlementinquiry#com.sap.isa.core.jmx.ext.ExtBootstrapper#Viw~t0yxJv!nzcjy*!6#67##n/a##157475101b0e11dfb011005056a31282#SAPEngine_Application_Thread[impl:3]_17##0#0#Error#1#/Applications/BusinessLogic#Java###Error in CCMS reporting: #1#unable to register MBeans#
24309   #1.5 #005056A3128200280000000000001AD800047FB938DA2ACD#1266333406410#/Applications/BusinessLogic#sap.com/crm~b2c#com.sap.isa.core.init.InitDescription.getInitializable#Guest#0##n/a##4c1152a01b0e11df8c0b005056a31282#SAPEngine_Application_Thread[impl:3]_36##0#0#Error#1#/Applications/BusinessLogic#Java###Initalization of failed.#1#com.sap.isa.advisor.backend.tst.AdvisorBackendTST#
24310   #1.5 #005056A31282002A0000000000001AD800047FB93AB6F382#1266333437660#/Applications/CRM_ICS_WFM/ICE/Default#sap.com/crm~wfdcs#com.saplabs.sis.opt.ServletBase.checkXCM(ServletBase.java:219)[hostXXX/]#Administrator#129##n/a##5eb1b1c01b0e11df9db4005056a31282#Thread[Thread-131,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Info#1#com.saplabs.sis.opt.ServletBase#Plain###(3131)Missing value for XCM configuration parameter 'cs.http.port'. A retry is scheduled in 30 seconds.[/Default]#
24311   #1.5 #005056A31282002B0000000000001AD800047FB93AB6FCE4#1266333437660#/Applications/CRM_ICS_WFM/ICE/Default#sap.com/crm~wfdcs#com.saplabs.sis.opt.ServletBase.checkXCM(ServletBase.java:219)[hostXXX/]#Guest#0##n/a##5eb1b1c11b0e11dfb98f005056a31282#Thread[Thread-129,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Info#1#com.saplabs.sis.opt.ServletBase#Plain###(3131)Missing value for XCM configuration parameter 'cs.http.port'. A retry is scheduled in 30 seconds.[/Default]#
24312   #1.5 #005056A31282002C0000000000001AD800047FB93AB6FF9E#1266333437660#/Applications/CRM_ICS_WFM/ICE/Default#sap.com/crm~wfdcs#com.saplabs.sis.opt.ServletBase.checkXCM(ServletBase.java:219)[hostXXX/]#Guest#0##n/a##5eb1b1c21b0e11dfa58b005056a31282#Thread[Thread-130,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Info#1#com.saplabs.sis.opt.ServletBase#Plain###(3131)Missing value for XCM configuration parameter 'cs.http.port'. A retry is scheduled in 30 seconds.[/Default]#
24313   #1.5 #005056A31282002F0000000000001AD800047FB93BC6D909#1266333455473#/Applications/BusinessLogic#sap.com/crm~cviews#com.sap.isa.core.init.InitDescription.getInitializable#Administrator#133##n/a##694fbe101b0e11dfcc96005056a31282#SAPEngine_Application_Thread[impl:3]_38##0#0#Error#1#/Applications/BusinessLogic#Java###Initalization of failed.#1#com.sap.isa.useradmin.handler.UseradminInitHandler#
24314   #1.5 #005056A3128200330000000000001AD800047FB93DD62A70#1266333490035#/Applications/Common/Infrastructure#sap.com/crmicss_b2c#org.apache.commons.digester.Digester#Guest#0##n/a##7de97c301b0e11df9146005056a31282#SAPEngine_Application_Thread[impl:3]_29##0#0#Error#1#org.apache.commons.digester.Digester#Java###system.forward.info#1#com.sap.engine.lib.xml.parser.NestedSAXParserException: com.sap.engine.lib.xml.parser.ParserException: Check whether the open and close tags are properly nested. (CharData is not allowed here.)(file://localhost/F:/usr/sap/EPD/JC10/j2ee/cluster/server0/apps/sap.com/crmicss_b2c/servlet_jsp/icss_b2c/root/WEB-INF/conf/struts-config.xml, row:118, col:9)(:main:, row=0, col=0) -> com.sap.engine.lib.xml.parser.ParserException: Check whether the open and close tags are properly nested. (CharData is not allowed here.)(file://localhost/F:/usr/sap/EPD/JC10/j2ee/cluster/server0/apps/sap.com/crm~icss_b2c/servlet_jsp/icss_b2c/root/WEB-INF/conf/struts-config.xml, row:118, col:9)#
24315   #1.5 #005056A3128200220000001000001AD800047FB961D04BAD#1266334093676#/Applications/Common/Infrastructure#sap.com/crm~b2b#com.sap.isa.maintenanceobject.backend.MaintenanceObjectHelper#UsernameXXX#234##hostXXX_EPD_101329050#UsernameXXX#e4dccfe01b0f11dfb50f005056a31282#SAPEngine_Application_Thread[impl:3]_11##0#0#Error#1#/Applications/Common/Infrastructure#Plain###Cache already initialized#
24316   #1.5 #005056A3128200220000001200001AD800047FB961F0F65E#1266334095816#/Applications/Common/Infrastructure#sap.com/crm~b2b#com.sap.isa.catalog.trex.TrexCatalogServerEngine#UsernameXXX#234##hostXXX_EPD_101329050#UsernameXXX#e4dccfe01b0f11dfb50f005056a31282#SAPEngine_Application_Thread[impl:3]_11##0#0#Warning#1#com.sap.isa.catalog.trex.TrexCatalogServerEngine#Java###Warning: #1#Invalid status 'DeletePending' for index df158fb17a0aebf19888005056a37c9edev020(CatalogKey: ZPC_EN)#
24317   #1.5 #005056A3128200220000001300001AD800047FB961F1C37B#1266334095879#/Applications/Common/Infrastructure#sap.com/crm~b2b#com.sap.isa.catalog.trex.TrexCatalogServerEngine#UsernameXXX#234##hostXXX_EPD_101329050#UsernameXXX#e4dccfe01b0f11dfb50f005056a31282#SAPEngine_Application_Thread[impl:3]_11##0#0#Warning#1#com.sap.isa.catalog.trex.TrexCatalogServerEngine#Java###Warning: #1#Invalid status 'DeletePending' for index df1657de7c2d2ff19888005056a37c9edev020(CatalogKey: ZPC_EN)#
24318   #1.5 #005056A3128200220000001400001AD800047FB961F25A6B#1266334095910#/Applications/Common/Infrastructure#sap.com/crm~b2b#com.sap.isa.catalog.trex.TrexCatalogServerEngine#UsernameXXX#234##hostXXX_EPD_101329050#UsernameXXX#e4dccfe01b0f11dfb50f005056a31282#SAPEngine_Application_Thread[impl:3]_11##0#0#Warning#1#com.sap.isa.catalog.trex.TrexCatalogServerEngine#Java###Warning: #1#Invalid status 'DeletePending' for index df17d4e1b2d57ff19888005056a37c9edev020(CatalogKey: ZPC_EN)#
24319   #1.5 #005056A3128200220000001500001AD800047FB961F2E857#1266334095941#/Applications/Common/Infrastructure#sap.com/crm~b2b#com.sap.isa.catalog.trex.TrexCatalogServerEngine#UsernameXXX#234##hostXXX_EPD_101329050#UsernameXXX#e4dccfe01b0f11dfb50f005056a31282#SAPEngine_Application_Thread[impl:3]_11##0#0#Warning#1#com.sap.isa.catalog.trex.TrexCatalogServerEngine#Java###Warning: #1#Invalid status 'DeletePending' for index df180971f2ad43f19888005056a37c9edev020(CatalogKey: ZPC_EN)#
24320   #1.5 #005056A3128200220000001600001AD800047FB961F403B4#1266334096019#/Applications/Common/Infrastructure#sap.com/crm~b2b#com.sap.isa.catalog.trex.TrexCatalogServerEngine#UsernameXXX#234##hostXXX_EPD_101329050#UsernameXXX#e4dccfe01b0f11dfb50f005056a31282#SAPEngine_Application_Thread[impl:3]_11##0#0#Warning#1#com.sap.isa.catalog.trex.TrexCatalogServerEngine#Java###Warning: #1#Invalid status 'DeletePending' for index df158fb17a0aebf19888005056a37c9edev020(CatalogKey: ZPC_EN)#
24321   #1.5 #005056A3128200220000001700001AD800047FB961F43A81#1266334096035#/Applications/Common/Infrastructure#sap.com/crm~b2b#com.sap.isa.catalog.trex.TrexCatalogServerEngine#UsernameXXX#234##hostXXX_EPD_101329050#UsernameXXX#e4dccfe01b0f11dfb50f005056a31282#SAPEngine_Application_Thread[impl:3]_11##0#0#Warning#1#com.sap.isa.catalog.trex.TrexCatalogServerEngine#Java###Warning: #1#Invalid status 'DeletePending' for index df1657de7c2d2ff19888005056a37c9edev020(CatalogKey: ZPC_EN)#
24322   #1.5 #005056A3128200220000001800001AD800047FB961F46D0E#1266334096051#/Applications/Common/Infrastructure#sap.com/crm~b2b#com.sap.isa.catalog.trex.TrexCatalogServerEngine#UsernameXXX#234##hostXXX_EPD_101329050#UsernameXXX#e4dccfe01b0f11dfb50f005056a31282#SAPEngine_Application_Thread[impl:3]_11##0#0#Warning#1#com.sap.isa.catalog.trex.TrexCatalogServerEngine#Java###Warning: #1#Invalid status 'DeletePending' for index df17d4e1b2d57ff19888005056a37c9edev020(CatalogKey: ZPC_EN)#
24323   #1.5 #005056A3128200220000001900001AD800047FB961F49D86#1266334096066#/Applications/Common/Infrastructure#sap.com/crm~b2b#com.sap.isa.catalog.trex.TrexCatalogServerEngine#UsernameXXX#234##hostXXX_EPD_101329050#UsernameXXX#e4dccfe01b0f11dfb50f005056a31282#SAPEngine_Application_Thread[impl:3]_11##0#0#Warning#1#com.sap.isa.catalog.trex.TrexCatalogServerEngine#Java###Warning: #1#Invalid status 'DeletePending' for index df180971f2ad43f19888005056a37c9edev020(CatalogKey: ZPC_EN)#
24324   #1.5 #005056A3128200340000000000001AD800047FB962954A0E#1266334106598#/Applications/UserInterface#sap.com/crm~b2b#com.sap.isa.isacore.DocumentHandler#UsernameXXX#234##hostXXX_EPD_101329050#UsernameXXX#e4dccfe01b0f11dfb50f005056a31282#SAPEngine_Application_Thread[impl:3]_33##0#0#Warning#1#com.sap.isa.isacore.DocumentHandler#Plain###b2b.dochandler.warn.notontop#
24325   #1.5 #005056A3128200290000004400001AD800047FB962D270BC#1266334110598#/Applications/UserInterface#sap.com/crm~b2b#com.sap.isa.isacore.uiclass.SalesDocumentBaseUI#UsernameXXX#234##hostXXX_EPD_101329050#UsernameXXX#e4dccfe01b0f11dfb50f005056a31282#SAPEngine_Application_Thread[impl:3]_20##0#0#Warning#1#com.sap.isa.isacore.uiclass.SalesDocumentBaseUI#Plain###UI parameter initial.newpos not set properly, 5 taken as default#
24326   #1.5 #005056A3128200350000000000001AD800047FB963A12DA7#1266334124145#/Applications/UserInterface#sap.com/crm~b2b#com.sap.isa.isacore.uiclass.SalesDocumentBaseUI#UsernameXXX#234##hostXXX_EPD_101329050#UsernameXXX#e4dccfe01b0f11dfb50f005056a31282#SAPEngine_Application_Thread[impl:3]_5##0#0#Warning#1#com.sap.isa.isacore.uiclass.SalesDocumentBaseUI#Plain###UI parameter initial.newpos not set properly, 5 taken as default#
24327   #1.5 #005056A3128200320000000100001AD800047FB963FE1C13#1266334130239#/Applications/BusinessLogic#sap.com/crm~b2b#com.sap.isa.core.eai.sp.jco.JCoConnectionStateful#UsernameXXX#234##hostXXX_EPD_101329050#UsernameXXX#e4dccfe01b0f11dfb50f005056a31282#SAPEngine_Application_Thread[impl:3]_21##0#0#Error#1#/Applications/BusinessLogic#Java###Error occcurred in EAI layer "".#2#com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: CPIC-CALL: 'CMRCV'
24328   null
24329   #parameters: [client]='null' [user]='null' [language]='null' [ashost]='null' [systemnumber]='null' [mshost]='null' [gwhost]='null' [gwserv]='null' [group]='null' [systemid]='null'
24330   Properties: {lang=en, passwd=?, sysnr=00, client=020, user=uname, ashost=hostXX, jco.client.type=A, maxcon=100, codepage=1100}
24331   Client not connected#
24332   #1.5 #005056A3128200320000000300001AD800047FB963FE781C#1266334130271#/Applications/UserInterface#sap.com/crm~b2b#com.sap.isa.isacore.action.order.MaintainBasketSimulateAction#UsernameXXX#234##hostXXX_EPD_101329050#UsernameXXX#e4dccfe01b0f11dfb50f005056a31282#SAPEngine_Application_Thread[impl:3]_21##0#0#Error#1#/Applications/UserInterface#Plain###A runtime exception occurred on the highest level#
24333   #1.5 #005056A3128200320000000500001AD800047FB963FEEFEB#1266334130302#/Applications/UserInterface#sap.com/crm~b2b#com.sap.isa.core.util.MessageListDisplayer#UsernameXXX#234##hostXXX_EPD_101329050#UsernameXXX#e4dccfe01b0f11dfb50f005056a31282#SAPEngine_Application_Thread[impl:3]_21##0#0#Error#1#/Applications/UserInterface#Plain###An exception has occurred: .#

What is CTS ? what is the role of CTS in between DEV and QAS?

Dear
What is CTS ? what is the role of CTS in between DEV and QAS?
Thanx & Regards
Mohamamd Nabi
[email protected]

hello, friend.
actually, you can search for subjects like this in the threads archive. you will be pleasantly surprised to find that there are already many threads with similar issues and that you can find answers to even more otherwise unrealized questions. and you don't have to wait for anyone to reply.
it looks like the issue is urgent for you, and this is why i am attaching this feed from Sadhu Kishore, which was posted some time ago... (if he replies to your thread, you may choose to award him points).
"Hi,
The transport workflow provides a framework for transporting enhancements or new developments of existing business functions in a system landscape. It provides a direct connection between development and transport administration. The transport workflow manages the transport process, determines the user for each individual step automatically, and then displays an interface which they can use to perform the task directly.
It is an efficient method of transporting a selected number of requests into a group of transport targets, and uses clearly defined approval steps to ensure the quality of your target systems. The requests can be transportable change requests, Customizing requests, relocation transports or transports of copies. The transport targets do not need to be located on defined transport routes. However, the transport workflow can involve some risks, caused by the dependencies between transport requests:
Import sequence
It is important that you import requests in the correct order, so that development work is up-to-date in the target system.
Incompleteness
It is important that the functions transported in the transport proposal are complete; otherwise errors may occur in the import system.
A request is not imported, but it contains an important data element. You use another request to transport a table that references this data element. Since the referenced data element does not exist in the target system, activation errors will occur when you import the second request.
The transport workflow is a generic workflow. Its ability to process the transport route configuration in TMS enables it to adapt itself to any system landscape. This means you can transport multiple requests into multiple targets, even if these targets are not located on the transport routes.
This reduces the amount of work for the transport administrator significantly. The automated nature of the workflow also reduces the likelihood of errors during transports.
You can use the transport workflow in two different ways.
Transport workflow as a transport strategy
If you have production systems in your landscape that can only accept approved transports, we recommend that you use the transport workflow to organize and coordinate the transport process.
To do this, set Workflow-controlled transports as your transport strategy and configure the transport workflow.
When you release a transport request, the transport workflow starts automatically and the screen Create Transport Proposal appears. The requests are then released implicitly when the transport proposal is sent to the transport administrator.
Special transport workflow (mass transports)
You can use the special transport workflow to make transports that do not follow the defined transport routes or that take place outside the normal transport schedule (part of the mass transport strategy). These transports may be corrections made in the development system that have to be transported into the production system without delay.
To use the special transport workflow, set Mass transports as your transport strategy and configure the transport workflow."
thanks. you have been most generous.
regards.

Sap SD resume

respected seniors,
I am new to the sap
will any body send your sample sap (SD) resumes please
my e_mail [email protected]
yours ever
Pankaj Kumar 

Dear Pankaj,
I guess we need to exchange our subject knowledge and clear doubts if any on the same, here on the forums. Let us use it for the same.
All the best.
Thanks & Regards
Sadhu Kishore
Message was edited by:
sadhu kishore

Euro customizing

Hi friends,
When I am doing sales order after giving the header data I am getting the following message " Pricing/euro: Attention: Euro Customizing not maintained ". Ofocurse if I ignore this, I am able to create sales order with out any problem as this is only information. But my doubt is why this message is coming and what should I do for not getting this message?
Dont tell me to maintain Euro customizing in SPRO.
Please tell me step by step procedure.
Friendly
Rama
Hi rama rao,
you just need to EWCF transaction and confrim Euro currency settings to avoid getting this message. Take proper approvals from your FI heads before you actually do it since currecny settings or for that matter global settings can also impact negatively if not done with proper understanding of the system -- in terms projects running, any changes being carried / in process.
To run EWCF, it just takes a minute.. you see four radio buttons > select *confirm euro currecny
customizing* > execute. We have done this recently.. so let me know if you any more questions.
regards
sadhu kishore
Kishore,
I have done this in test client and working fine. But when I tried this in production it is giving error like this " Customizing of currencies for the euro is missing or incomplete ". Then after enter it is giving error " Euro currency Customizing was not confirmed ".
For this I have maintained EURO customizing in different places. But still the same error is coming.
So now can you tell me what to do next.
Kindly try to help me out of this.
Regards
Rama

Dear Rama Rao
You said that in test client, it is working and not in production. So please compare both the settings and I am sure, some setting is missing in production compared to test client.
For more information, please go through this Building Block
[External Accounting|http://help.sap.com/bestpractices/BBLibrary/documentation/Q70_BB_ConfigGuide_EN_DE.doc]
thanks
G. Lakshmipathi

Userexit for not allowing release order qnty greater than contr targt qnty

hi,
I posted the same mail before, but it seems we cannot do it in configuration..plz provide me a suitable User exit for the same..
When i am creating a release order for a quantity contract, the system is allowing to save the doc if at all the quantity is more than in the contract, i.e. if the user changes the quantity in release order more than the contract quantity, the system is issuing a warning message and allowing to save.(mess no V1 501)
I want to change this warning to an error message..
I checked in OVAH but only V4 messages are available there..
In SE91 i am able to see the message but there is no way for any change..
Thanks,
Sam

hi Sadhu Kishore,
In VTAA..from qnty contract to sales order in item level document flow is updated...the following is assigned there
Create doc. flow records except for dely/goods issue/billdoc
I searched some previous threads of the same characteristics, so everybody is telling the solution will be a user exit...
plz help reg thiss
Thanks,
Sam

SD CIN

Hi all,
pls provide study material on SAP SD CIN. is there any difference betwen SD CIN & MM CIN.
thanx well in advance
pls mail at
[email protected]

CIN:
IMG > Logistics - General > Tax on Goods Movement > India > Basic Settings >
Maintain Excise Registrations
Use
In this IMG activity, you maintain the data relating to your excise registrations.
Activities
Enter each of your excise registrations, specifying a four-character code for each
Excise Registration IDs
In this activity, you maintain excise registration IDs. You create one ID for each of your business's excise registrations.
Activities
For each excise registration in your business create a registration ID and state:
Ï Which taxes the registration covers (additional excise duty, special excise duty, and cess)Fields for any taxes that are not covered will be hidden in transactions involving excise duty.
Ï The maximum number of items to be printed on each excise invoice
Ï Whether you are allowed partial CENVAT credits
Maintain Registration ID NUMBER, Excise code number, excise registration number
Excise Registration Number
A number assigned to each premises or location that has registered as a manufacturer with the excise authorities.
Every entity with an excise registration number is required to keep its own excise books.
ECC Number
Specifies the organization's ECC number.
Excise Registration Number
A number assigned to each premises or location that has registered as a manufacturer with the excise authorities.
Every entity with an excise registration number is required to keep its own excise books.
Excise range: Specifies the excise range in whose area the excise registration is located.
Excise Division
Specifies the excise division in whose area the excise registration is located.
Excise Collectorate
The code of the excise collectorate in whose area the excise registration is located.
Indicator for confirming AED usage
Additional Excise Duty Percentage. These are leviable under the additional duties of excise act. These duties are in addition to basic excise duty and special excise duty.
Example
Additional Excise duty is leviable in case of textile products, tobacco and sugar.
Similarly for SED CESS
Number of Items in Excise Invoice
Shows the maximum number of line items that the authorities allow per excise invoice.
Dependencies
This information is used when you create an excise invoice in Sales and Distribution (SD) for factory sales and for other movements.
This information is used to split the transfer postings' items into multiple subcontracting challans.
Excise register set description
Description of the excise registers set.
Partial CENVAT Credit
Indicates that the excise registration ID is allowed to credit only a portion of its input excise duty to its CENVAT account.
Dependencies
When you post a goods receipt, the system splits the input excise duty on the material into its deductible and nondeductible amounts. It posts the deductible duty to the appropriate CENVAT account, and adds the nondeductible duty to the material value.
This information is also shown when you post the vendor's excise invoice.
Maintain Company Code Settings
Use
In this IMG activity, you maintain the data relating to your company codes.
Document Type for CENVAT Postings
It controls, which document type the system uses when making CENVAT postings in Financial Accounting (FI). Here ED is document type for cenvat posting.
Indicator for providing debit account overwriting
Debit Account Overwrite Indicator. X - Indicates debit accounts can be overwritten. Use In excise journal voucher transaction. It provides the flexibility to the user to enter the debit account of his choice depending on the nature of transaction.
Automatic balance Indicator
Excise year start month
The calendar month marking the beginning of the excise year
Use
This start month represents the month for the start of the excise invoice number range. The month 04 is entered here indicating April of the calendar year as the start month for excise invoices. Any change by the Excise authorities regarding start month should be taken care of by an entry in this field and initialization.
Excise invoice selection procedure
Excise invoice selection type. To indicate the method opted by the company for selecting the excise invoice. It can be either earliest or latest invoices that were received.
Number of excise invoices to be selected
Indicates the number of excise invoices that needs to be selected in the excise invoice selection.
Days to be considered for excise invoice selection
Number of days from document date for excise invoice selection.
Example
If the value of this field is 20 and today is 28-03-97. The excise
invoice selection will show the related invoices only for the
period 08-03-97 to 28-03-97.
Document type for TDS FI posting
Financial accounting document type for TDS posting.
Document type for FI posting on Utilisation
Financial accounting document type for TDS posting.
Indicator for item level excise duty round off
This indicator is to be used for deciding whether Item level excise duty amount rounding off is required during procurement cycle. If marked 'X' then the excise duty amount will be rounded off to the nearest rupee at the Purchase order level. This will not round off the CENVAT credit to be taken. If the duty amount is less than one rupee then no rounding is done
Rounding off of Excise duty for outgoing excise invoice
You can round off the Excise amount to be paid during an outgoing Excise invoice by marking this indicator as 'X'. The rounding is done at the item level for each item where the amount is greater than 1 Rupee.
Immediate Credit on Capital Goods
Instructs the system, when you verify a goods receipt for capital goods, to immediately post half of the input excise duty to the appropriate CENVAT accounts.
The rest is posted the CENVAT on hold account, for use in the following year.
CVD Clearing Account
Specifies which G/L account the system credits when you take a CENVAT credit on countervailing duty in the Incoming Excise Invoices transaction.
Exchange rate type
Key representing a type of exchange rate in the system.
Use
You enter the exchange rate type to store different exchange rates.
Example
You can use the exchange rate type to define a buying rate, selling rate, or average rate for translating foreign currency amounts. You can use the average rate for the currency translation, and the bank buying and selling rates for valuation of foreign currency amounts.
Exchange rate type to be used for Export excise duty converts
When you are creating an Excise invoice for export sales then the exchange rate for duty calculation will be picked up using this Exchange rate type.
Maintain Plant Settings
Use
In this IMG activity, you maintain excise information relating to your plants.
Plant Settings
In this activity, you maintain excise information relating to your plants.
Activities
For each plant:
? Specify whether it is a manufacturing site or a depot.
? Assign it an excise registration ID.
You can assign the same ID to more than one plant, if required.
Depot
Indicates that the plant in question is a depot.
Dependencies
Depots are required to prepare register RG 23D, and follow different procedures for goods receipt and invoice generation.
Number of goods receipt per excise invoice.
Multiple GR for one excise invoice, Single credit
Multiple GR for one excise invoice, Multiple credit
Maintain Excise Groups
Use
In this IMG activity, you define your excise groups. For each excise group, you can also control how various excise invoice transactions will work.
Excise Groups
In this activity, you define excise groups. An excise group allows you to maintain a separate set of excise registers and excise accounts. The RG 23A, RG 23C and PLA serial numbers are created for an excise group.
Recommendation
Under normal circumstances, excise authorities require every business to maintain only one set of excise registers and one set of accounts. But through exemption from the authorities, multiple books can be maintained.
If your company has only one set of excise registers, then you need to maintain only one excise group.
Activities
1. Create one excise group for each set of registers that you need to keep.
1. Assign the excise groups to plants.
2. Maintain whether this Excise group is for a depot or not.
3. If you receive only one consignment for an Excise challan then you can leave GR's per EI as blank. If you receive multiple GR's for a given Excise challan and would like to avail multiple credit mark the GRs per EI as 'Multiple GR's for one excise invoice, multiple credit'. Alternatively if you want to availa the credit only after all the goods receipts have been made mark it as ' Multiple GR for one excise invoice, single credit'.
4. If you want to automatically create Excise invoice during Sales cycle at the time of billing the tick the indicator 'Create EI'
5. During depot sales if you do not want to do RG23D selection and posting separately and would like to complete RG23D selection in one step mark the indicator 'RG23D Auto post'. This will post the selected records into RG23D automatically. You cannot cancel the selection later.
6. If the indicator 'Default GR qty' is marked system will default the Excise challan quantity on to the Goods receipt if the Excise invoice number is given in the pop-up.
7. If the indicator 'Folio no create' is marked system will generate Folio numbers for RG23D during receipt of excise invoice into depot.
8. 'Automatic posting' when ticked will post the Excise invoice other movements automatically along with creation in single step.
9. 'Create Part1 for Block Stock' when marked will create a Part1 during the receipt of material into Blocked stock .
10. 'Create Part1 for STO' when marked will create a Part1 during the receipt of material through inter plant transfers.
11. 'Create Part1 for consumption stock' when marked will create a Part1 during the receipt of material into consumption stock.
Excise Group
Governs which set of excise registers a business transaction will be included in.
Following is the relation between excise group, plant and registration.
Dependencies
In define excise groups in Customizing.
Then, in transactions involving excise duty, for example, when you post a vendor's excise invoice, you specify which excise group you are using. This information tells the system which G/L accounts to post the excise to.
At the end of the period, when you come to prepare your excise registers, you create different sets for each excise group.
Indicates that the plant in question is a depot.
Dependencies
Depots are required to prepare register RG 23D, and follow different procedures for goods receipt and invoice generation.
GR Per Excise Invoice
Multiple GR for one excise invoice , Multiple credit
Multiple GR for one excise invoice , Single Credit
Create Excise Invoice Automatically
Instructs the system to automatically create a Sales and Distribution (SD) excise invoice immediately you create a commercial invoice or a pro forma invoice.
The excise invoice is created in the background.
Dependencies
If you want to make use of this function, you must also define the default plant, excise group, and series groups in Customizing for Sales and Distribution (SD), by choosing Excise Group - Series Group Determination.
RG23D Sales Creation and posting option
RG23D Automatic Option if selected will create Depot excise invoice by posting the selection of excise invoices in single step.
If this is not selected then you need to separately do RG23D selection followed by PGI and then RG23D verification and posting.
If you need automatic posting of RG23D selection then the Post Goods Issue should have been completed before running RG23D selection.
Default excise qty in GR
If this indicator is ticked then while doing Goods Receipt using 'MB01' system will default the excise invoice quantity on to the Goods receipt document.
Folio number for depo
Posting
If this indicator is marked then while creating Excise invoice for other movements system automatically does the Verify and Post. You need not separately Post the excise invoice
Also we can set indicator for creation of part 1 for:
Blocked stock
Stock transport order
Consignment stock
Maintain Series Groups
Use
In this IMG activity, you define the different excise series groups within your company. Series groups allow you to maintain multiple number ranges for the outgoing excise documents.
Based on excise regulations and exemptions from the authorities you can maintain multiple number series for outgoing documents. But each of these series has to be declared to the excise authorities.
Activities
? Define excise series groups based on type of outgoing document
? Assign series group to excise registration ID
? If no financial postings are required for an Excise invoice in this seris group then you tick the 'No utilization' indicator.
? If the CENVAT has to be paid immediately and you need not wait for the Fort nightly payment then mark the 'Immediate Utilization' indicator.
Example
You could define two series groups, group 001 for excise invoices, and group 002 for 57 F4 documents.
No account postings for CENVAT in sales cycle
No utilization Flag
If you do not need any CENVAT utilization for an excise invoice but would like to just generate an excise invoice then you need to mark this indicator.
IF the flag is checked then system will create an Excise invoice in the given Series group but there will not be any account postings or Part2 postings.
Immediate Utilization of CENVAT
Specifies that when you create an excise invoice, the system immediately pays the amount from CENVAT and creates the Part II entry. Such invoices will not be listed for fortnightly utilization.
If you have both fortnightly and immediate utilization for the same excise group, the account determination within CIN IMG should point to the ED interim account.
Account determination for immediate payment will be done exactly the same as being done for fortnightly utilization program.
Maintain Excise Duty Indicators
Use
In this IMG activity, you maintain the excise duty indicators.
IMG > Logistics - General > Tax On Goods Movement > India > Basic Settings > Determination of Excise Duty >
Select Tax Calculation Procedure
Use
In this IMG activity, you specify which tax procedure you want to use for determining excise duties and sales taxes on input materials in India.
? If you use condition-based excise determination, use a copy of the tax procedure TAXINN.
? If you use formula-based excise determination, use a copy of the tax procedure TAXINJ.
This tax procedure also supports condition-based excise determination, so that you can work with both concurrently.
We strongly recommend that new customers use condition-based excise determination. Note that once you have started using a tax procedure, you cannot switch to another one, otherwise you will not be able to display old documents.
Maintain Excise Defaults
Use
In this IMG activity, you define which tax procedure and pricing condition types are used in calculating excise taxes using formula-based excise determination.
Activities
If you use condition-based excise determination, fill out the CVD cond. field and leave all the others blank.
If you use formula-based excise determination, fill out all of the fields as follows:
? Enter the tax procedure and the pricing conditions that are relevant for excise tax processing.
? Specify the purchasing and sales conditions types used for basic excise duty, additional excise duty, special excise duty, and cess.
? Specify the conditions in the sales order that are used for excise rates.
? Specify the countervailing duty condition type used for import purchase orders.
See also
SAP Library -> Logistics -> Country Versions -> Asia-Pacific -> India -> Materials Management (MM) -> Condition-Based Excise Determination and -> Formula-Based Excise Determination.
IMG > Logistics - General > Tax On Goods Movement > India > Basic Settings > Determination of Excise Duty >
Condition-Based Excise Determination
Use
When you enter a purchasing document, for example, a purchase order, the R/3 System automatically calculates the applicable excise duties using the condition technique.
Features
The standard system comes with two tax calculation procedures. TAXINN is only supports condition-based excise determination, whereas TAXINJ supports condition-based excise determination and formula-based excise determination. Both tax procedures contain condition types that cover all of the excise duties and sales taxes applicable.
Since the exact rates of excise duty can vary on a large number of factors, such as which vendor you purchase a material from, or which chapter ID the vendor stocks the material under, you create condition records for every sort of excise duty.
When you come to enter a purchasing document, the system applies the excise duty at the rates you have entered in the condition records.
Activities
Customizing
Make the settings in Customizing Basic? India?for Logistics - General, by choosing Taxes on Goods Movements Account? Excise Duties Using Condition Technique and ...?Settings Determination.
These activities include one activity where you define a tax code for condition-based excise determination.
Master Data
Create condition records for all excise duties that apply, and enter the tax code for condition-based excise determination in each.
Day-to-Day Activities
When you enter a purchase order or other purchasing document, enter the tax code for condition-based excise determination in each line item. The system then calculates the excise duties using the condition records you have created.
When the ordered materials arrive, you post the goods receipt and the excise invoice. The system posts the excise duty to the appropriate accounts for deductible input taxes when you enter the excise invoice.
Creating Condition Records for Excise Duty
1. In the command field, enter FV11 and choose .
2. Enter the condition type that you want to create a condition record for and choose .
The Key Combination dialog box appears.
3. Select the combination of objects that you want to create the condition record for.
On the dialog box, Control Code means "chapter ID."
So, for example, to create a condition record for a tax that applies to a combination of country, plant, and chapter ID, select Country/Plant/Control Code.
4. Choose .
5. Enter data as required.
In the Tax Code field, enter the dummy tax code that you have defined.
6. Save the condition record.
Formula-Based Excise Determination
Use
When you execute a business transaction involving materials that are subject to excise duty, the system automatically calculates the duty for you.
Prerequisites
In order for the system to be able to determine which rate of excise duty to apply, you must have maintained all the data on the Excise Rate Maintenance screen, which you can Master Data?access from the SAP Easy Access screen by choosing Indirect Taxes Excise Rate Maintenance.?
You maintain the following types of data:
? Plant master data
You assign each of your plants an excise duty indicator. You can use the same indicator for all the plants with the same excise status from a legal point of view, such as all those that are in an exempt zone.
See also the information about manufacturers that are only entitled to deduct a certain portion of the duty (see Partial CENVAT Credit).
? Vendor master data
For each of your vendors with the same excise status from a legal perspective, you define an excise duty indicator. You must also specify the vendor type - for example, whether the vendor is a manufacturer, a depot, or a first-stage dealer. You must also stipulate if the vendor qualifies as a small-scale industry.
For each permutation of plant indicator and vendor indicator, you then create a final excise duty indicator.
? Customer master data
Similarly, you assign the same excise duty indicator to each of your customers that share the same legal excise status.
Again, for each permutation of plant indicator and customer indicator, you then create a final excise duty indicator.
? Material master data
Each material is assigned a chapter ID.
? Excise tax rate
For every chapter ID and final excise duty indicator, you maintain the rate of excise duty.
If your business only qualifies for partial CENVAT credit, you must customize your system accordingly.
Activities
Let us consider an example to illustrate how the system determines which rate of excise duty to apply to a material. Assume you are posting a sale of ball bearings to a customer. The system automatically determines the rate of excise duty as follows:
1. Looks up the customer master data to see what status you have assigned the customer.
Let's assume you've assigned the customer status 3.
2. Looks up the plant master data to see what status you have assigned the plant.
Similarly, your plant has status 2.
3. The system looks up the table under Excise Indicator for Plant and Customer to see what the final excise duty indictor is for customer status 3 and plant status 2: It is 7.
4. The system determines the chapter ID of the ball bearing for the plant.
Let's assume the chapter ID at plant for the ball bearings is 1000.01.
5. Finally, the system looks up the table under Excise Tax Rate to see what rate of duty applies to chapter ID 1000.01 under status 7.
Define Tax Code for Purchasing Documents
Use : In this IMG activity, you define a tax code for the purposes of calculating excise duty when you enter purchasing documents.
Only carry out this activity if you use condition-based excise determination.
Activities: Create a new tax code, and set the tax code type to V (input tax). Do not make any other settings for it.
Assign Tax Code to Company Codes
Use
In this IMG activity, assign the tax code for purchasing documents to the company codes where it will be used.
Only carry out this activity if you use condition-based excise determination.
Classify Condition Types
Use
In this IMG activity, you specify which condition types you use for which sort of tax. Note that this only applies to condition types that you use with the new excise determination method.
The system uses this information when you create a document from another one. For example, when you enter an incoming excise invoice from a purchase order, or when you create an outgoing excise invoice from a sales order, the system determines the various excise duties in the excise invoice using the information that you have entered here.
In addition, when you create a purchasing document, the system only uses the condition types that you enter here.
? For taxes on purchases, use the condition types contained in the tax procedure.
? For taxes on sales, use the condition types contained in the pricing procedures.
Standard settings
The standard system comes with sample settings for the tax calculation procedures and pricing procedures.
Use these settings as a basis for your own.
IMG > Logistics - General > Tax On Goods Movement > India > Account Determination
Define G/L Accounts for Taxes
Use
In this IMG activity, you specify which G/L accounts you will use to record which taxes.
Requirements
You have set up G/L accounts for each of the processing keys listed below.
Activities
Assign an account to each of the following posting keys. The accounts for VS1, VS2, and VS3 are used as clearing accounts during excise invoice verification.
? VS1 (basic excise duty)
? VS2 (additional excise duty)
? VS3 (special excise duty)
? VS5 (sales tax setoff)
? MWS (central sales tax)
? MW3 (local sales tax)
? ESA (service tax)
? ESE (service tax expense)
Specify Excise Accounts per Excise Transaction
Use
In this IMG activity, you specify which excise accounts (for excise duty and CENVAT) are to be posted to for the various transaction types. Enter all the accounts that are affected by each transaction type.
If you use subtransaction types, enter the accounts for each subtransaction type as well.
Activities
Transaction type UTLZ is used for determining accounts only while posting excise JVs and also if the payment of excise duty has to be done fortnightly.
The fortnightly CENVAT payment utility picks up the credit side accounts from the transaction types of GRPO, EWPO, and TR6C for determining the CENVAT and PLA accounts. There is no separate transaction type for fortnightly payment.
Example
Excise TT DC ind Account name
GRPO CR CENVAT clearing account
GRPO CR RG 23 BED account
GRPO DR CENVAT on hld account
Specify G/L Accounts per Excise Transaction
Use
In this IMG activity, you assign the excise and CENVAT accounts to G/L accounts.
When you come to execute the various transactions, the system determines which G/L accounts to post to by looking at the:
? Excise group
? Company code
? Chart of accounts
Furthermore, if you want separate account determination settings within an excise group, you can also use sub transaction types.
Requirements
You have already:
? Defined the G/L accounts
? Defined the excise groups
? Maintained the transaction accounts
Activities
For each excise group, assign the excise and CENVAT accounts to G/L accounts. For most businesses, one set of accounts will suffice for alltransactions.
Note
You need not remit the CENVAT to the excise department immediately, so maintain the credit account for transaction type DLFC as an excise duty interim account. This will be set off when you remit the duty.
Config setting needed to be done in order to get the Excise Details Screen in Material Master.
Even though this functionality is available in enterprise version, a small config step has to be made in Screen Sequences for Material Master.
Following document helps you to do this configuration.
? Material Master ? Logistics General ?1. Go to IMG Define Structure of Data Screen for each?Configuring the Material master Screen Sequence.
2. Select your screen sequence. Usually it would be 21. Select the same and click on Data Screen in the left frame.
3. Once the data screens are exhibited, select data screen no. 15, ie. SSq. 21and Scrn 15, which is "Foreign Trade: Import Data". Select the same and click on Subscreens in the left frame.
4. Go to the last sub screen i.e. 21-15-6 - SAPLMGD1- 0001 and select the same. Click on tab view subscreen and ensure that the subscreen is blank.
5. Now in the last sub screen i.e. no.6 you delete SAPLMGD1 - 0001 and instead add SAPLJ1I_MATERIAL_MASTER and in the screen no. 2205.
6. Save the setting.
7. Create a Material Master and check whether in Screen Foreign Trade - Import, Excise related subscreen appears.
Back to ERP Operation Home.
Transaction Codes for India
Transaction
Action
J1I2
Prepare a sales tax register
J1I3
Create outgoing excise invoices in batches
J1I5
Update the RG 1 and Part I registers
J1IEX
Incoming Excise Invoices (central transaction)
J1IEX_C
Capture an incoming excise invoice (excise clerk)
J1IEX_P
Post an incoming excise invoice (excise supervisor)
J1IF01
Create a subcontracting challan
J1IF11
Change a subcontracting challan
J1IF12
Display a subcontracting challan
J1IF13
Complete, reverse, or recredit a subcontracting challan
J1IFQ
Reconcile quantities for subcontracting challans
J1IFR
List subcontracting challans
J1IH
Make a CENVAT adjustment posting
J1IIN
Create an outgoing excise invoice
J1IJ
Assign excise invoices to a delivery for sales from depots
J1INJV
Adjust withholding tax Item
J1INREP
Reprint a withholding tax certificate for a vendor
J1IQ
Year-End Income Tax Depreciation Report
J1IR
Download register data
J1IS
Process an excise invoice (outgoing) for other movements
J1IU
Process exemption forms
J1IW
Verify and post an incoming excise invoice
J1IX
Create an incoming excise invoice (without reference to purchase order)
J2I8
Transfer excise duty to CENVAT account
J2IU
Remit excise duty fortnightly
J2I9
Monthly CENVAT return
J1IG
Excise invoice entry at depot
J1IGA
Create additional excise entry at depot
J2I5
Extract data for excise registers
J2I6
Print excise registers
Sadhu Kishore
Posts: 2,518
Registered: 11/27/06
Forum Points: 4,324
   Re: cin
Posted: Feb 11, 2008 9:12 AM    in response to: shiva       E-mail this message      Reply
hi,
pl check this link :
CIN
regards
kishore

To cancell the billing documents in thousands

Hi friends,
Could you please suggest the best way to cancell the billing documents in thousands.
Thanks
Ranjan

Dear G. Lakshmipathi/Sadhu kishore,
First of all thanks for your valuable comments & the expected solution given by Sadhu kishore ( since i have not tried yet).
OK. Coming to the real problem : Thousands of documents are created in a particular date on which the exchange rate maintainance was not correct with respect to the particular translation date, by mistake by the user.
Now the exchange rate maintainance is corrected. But this needs to be populated in those invoices.
Please suggest.
Any clarification, please ask me.
Thanks a lot friends,
Ranjan

Maintaining Email address in VV31

Hello Experts,
My need is to send invoice to customer via Email (PDF).
I arrived to do it using output type with option: External send (Medium 5) but I had to specify the customer Email in the master data TR: XD02. And it's nicely done.
My main question is:
- Is it possible to manage Email address in Transaction VV31 without updating customer master data ?
- If yes, which function should I choose (MA, MP, BP ,...) when adding new condition record in VV31 ?
- The Email address should be assigned to the field partner ?
Last question:
- When using transmission medium 7 (internal) the mail will arrive as a blank PDF... I don't know why...
- What's the difference between Medium 5 (External send) and 7 (internal).
Thank you in advance for your help.
Regards,
Moez.

Hi all,
To Meher Souayeh: Thank you for your direct response.
To SVP4SD: I performed my test with:
Medium 5 option 4
I filled my E-mail address in the advised field: Cover Page Text
Communication strategy set to: CS01
But, I don't understand why I must choose Medium 1 and option 4
For me I have to work with Medium 5 and option doesn't matter.
To Sadhu Kishore: The final user want to avoid a fixed mail value for each customer and assign mail when validating the invoice (Even change it).
I have the same point of view as Sadhu Kishore and Meher Souayeh and I'm convinced that the better way to achieve this issue is by updating Master Data.
But if someone have another issue it will be very interesting.
Regards,
Moezz.

Sap fields

Hi all,
What are the SAP fields of a material for these description
1.Anticipated Annual Usage/Consumption
2.Recommended Max Stock
3.RECOMMENDEDMINIMUMSTOCK
4.INTERNALCOMMENT
5.SHORTTEXT
6.CLASS
7.STORAGECONDITIONS
8.PLANNEDDELIVERYTIME
how many export parameters can we declare in a Fm?

Your question is so broad and cannot be easily answered here. As rightly suggested by Sadhu Kishore, whichever field details you would like to know, place your mouse on that particular field and press F1 so that it will give a detailed explanation.
Just to give you a small explanation, Document date is nothing but the date of creation of that document; goods issue date is the date on which, you post the goods issue.
thanks
G. Lakshmipathi

Problem in COPA re-initialization - Kishore Seereddi

Hi Kishore or other Gurus,
               I have an issue on my COPA values. KE24 doesn't reconciled with the values on my COPA cube. My initial conclusion is that some of the records created on October 2, 2008 and posting date on September 30, 2008.
               Is there an issue with the creation and posting date? or is there an issue on reinit because there is a reinitialization happen on October 2, 2008. I am not the one who do the reinitialization I am just supporting the issue.
              I mentioned Kishore here because I read on the thread below that he mentioned that we need to run the delta load up to 3 times the delta load retrieved only 0 records before doing init without data transfer and full repair. What is the reason behind these?
Re: COPA Enhancement and Reinit of Delta
             I asked because the guy who re-init the data delete the records of the cube and then just do init without data transfer and then full repair.
             Then the data where not synched between KE24 and COPA. The datasources is 1_COPA****.
             Hope you can help me asap. I will assign points asap too.
Thanks and regards,
Raymond
Edited by: Raymond Dela Cruz on Oct 27, 2008 11:20 AM

Hi,
As i understood that the Delta need to be loaded for 1 or more time in case of LO dataextraction, by doing so we clear the delta queue in LBWQ T-code. so this will not cause problem duplication of records in our next delta extraction.
For the CO-PA and FI the extraction method is different in compare to LO extraction. so there is no need to do the delta extraction before reinit of data.
Please check your filters in KE24 and BW are same during reconciliation. Because selection filters are important in COPA.
If you are looking for sales information, in KE24 check the corresponding invoice numbers created on date of intrest are available in COPA infocubes. this is one of the method.
Regards,
Vishwa.
Edited by: Vishwanath H.E on Oct 28, 2008 12:55 PM

ACCOUNT DETERMINATION "INTERCOMPANY SALES &3RD PARTY SALES" -kishore,AK ,

HI ,
 Rajesh , Kishore , AK ,
 well 2day i had client interview , he was very much stressing on " ACCOUNT DETERMINATION " process in intercompany sales , both in ordering comapny and delvering plant .
 At the same time account determination for 3rd party sales . well got some docs had brief capsule study , still stuck up .
 can u pl throw come clarity .
Regards,
jerry

Dear Jerry
Inter-Company Scenario in SAP is quite different than its literal meaning.
Inter-Company means, customer gives order to company code A (PlantA), but Plant A is not having stock, so it passes on to Plant B(CoCd B).So in Sales order of A you enter Plant B.
So now goods are delivered by Plant B to Customer and commercial invoice for customer is from CoCd A.
Cocd B just gives inter company invoice.
Now Comming to account determination , it totally depends on pricing procedure as account keys are there. There is not much difference from standard scenario, but you can have seperate G/L Accounts
If you are talking about sales between different company codes, then this can be handled having different sales document and thus different pricing procedure, you can ask customer , what is there requirement. and can say that it is like normal sales cycle only
Third-Party Processing
1) two standard process provided by SAP in the frames of the third-party processing:
a) pure third-party process: X creates the sales order, automatically purchase requision and later a purchase order will be created at the vendor. Then the vendor sends the goods directly to your customer and send the invoice to X. The company X creates the invoice to the customer Y.
b) individual purchase order: the same process, but the vendor sends the goods not to the customer directly, but first to X, and then the company X delivers the goods to the customer Y. The invoice is coming from Z to X (transaction MIRO), and then X creates invoice to Y.
you can refer the accounting document to get Idea of account determination
Regards
Jitesh

Rajesh/Sadhu/RobertoUrgent :- Open Sale Order Value not getting Reduced?

Hi,
   Upon Executing FD33 and clicking the status view for a Customer say XYZ , and then choosing EXTRAS-Open Sale Order . Say the value of open sale orders being shown is 75000. Even after closing the open sale orders (By Selecting VA05 and Putting reason for Rejection), and then also the Open Sales Order value is not getting diminished.
   What could be the reason ?
   Pls help.
Regrds,
Binayak
Message was edited by:
        Binayak Ghosh
Message was edited by:
        Binayak Ghosh

Hi Binayak,
As mentioned by you, running of Credit re-org program 'RVKRED77' is the only solution for this problem and it is known problem in SAP.
Some precautions
1. Always run the program in background by scheduling a job.
2. The idle time is around midnight when no user is working on SAP.
3. Some time the job fails as some other program may be updating same tables as this program. In such cases re-schedule the job at different time.
4. You may run the program 'RVKRED88' which will simulate without actual updation of credit values.
Hope this clarifies..
Regards,
Madhu.

To mr sadhu kishore

Similar Messages

Maybe you are looking for