Separate CIN (excise) GL accounts required at product level and plant level

Hi
Our client have one plant. It have two division - A and B. But excise registeration is one.
In SAP we have created two separate plants and two separate profit centers for two divisions A and B.
There are three products in A and two products in B. I believe that all CIN related settings and excise group can be assigned to a plant and not at a product level.
Now my client want product-wise stock and duty paid amount with PLA, RG23A and RG23C. Further they want to separately show clearance made without duty separately. Right now they are able to post product-wise JV in excise GL accounts so they have separate GL accounts at product level.
In SAP i believe that i cannot create separate CIN GL accounts separately for each products.
Please help. How to satisfy client's requirement.

Hi,
You can develop a new report with the help of ABAPer and provide it to the client.
Regards,
Hansa Chechani

Similar Messages

Capture Excise on Purchase through 1st Level and 2nd Level

Dear all,
Please clear about the Functionality to Capture Excise on Purchase through 1st Level and 2nd Level Dealer Invices in details please.
Regards,
Vishal

hi,
for dealer invoice we first do j1iex here we capture the excise duties
then we do migo &
again we do j1iex to post the excise invoice.

CIN: Excise invoice accounting document is incorrect - MIGO

Dear All,
In MIGO, the Material document has two items (both are Consumables with the same chapter ID) for which the excise invoice has been posted successfully. The RG23C Part 2 register is updated correctly.
But the accounting document so created has postings for only the second item. The posting for the first item is missing.
We have checked for the settings for 'Multiple goods receipt, Multiple credits' in Plant Settings and also in Excise Registration which is set.
Both the items in the Material document have the same tax code.
We have checked for the excise GL accounts.
The Excise GL accounts have been configured to GRPO
We have also checked the J_1IPART2 table. and the accounting document updated with BED, AED, ECS and SeCEss amounts are correct.
But what puzzles me is, when we check the accounting document in FB03, it has postings for only one item.
We have checked the configurations and everything seems fine. We have simulated this situation in Quality system and it works fine, i.e .the accounting document has postings for both the items. Problem here looks like, itu2019s a manual error. Since all the tables are updated, and only the accounting part is missing, is it ok, if we create a manual accounting document?
Can you please suggest?
Many thanks in advance
Vinod P

You are saying materials are consumables and registered in RG23C. This register is for Captial goods and not for consumables. I think it could be RG23A. check once again.
Check J1ID for both materials and compare. I am sure some of the details were missed here. Even blank field will not allow to post
Srinivas

Requirement to select material and plant ?

Hi,
i have below requirement .
I have selection screen ..in which material number as selections option and plant as parameters.
when ever user executes report i have store the material , plant , stlal(this field is in MAST table ) which are in selection screen in to one internal table based on following conditions.
stlan = 1 (BOM usage - in table MAST)
mtart = AA or UT (In Mara table)
stlal which is having minimum value.
I think i have to use inner join on these tables ...
please give me sample code ..please help...
thanks
satish

Check the sample program :
REPORT ZTEST_AMEM1.
tables : lfa1.
data : begin of i_lfa1 occurs 0 ,
       lifnr like lfa1-lifnr,
       name1 like lfa1-name1,
       land1 like lfa1-land1,
       end of i_lfa1.
start-of-selection.
select lifnr
       name1
       land1 from lfa1
       into table i_lfa1 up to 100 rows.
Export
export i_lfa1 to memory id 'SAP'.
submit ztest_amem2 and return.
write:/ 'hello'.
*& Report ZTEST_AMEM2
REPORT ZTEST_AMEM2.
data : begin of j_lfa1 occurs 0,
       lifnr like lfa1-lifnr,
       name1 like lfa1-name1,
       land1 like lfa1-land1,
       end of j_lfa1.
start-of-selection.
import i_lfa1 to j_lfa1 from memory id 'SAP'.
loop at j_lfa1.
write:/ j_lfa1-lifnr,j_lfa1-name1,j_lfa1-land1.
endloop.
Use submit command ,please press f1 on submit ,you get good documentation.
Thanks
Seshu

Consumptin Account Required for Production Order

While i am creating production order in CO01, it is showing the following error.
Consumption account cannot be determined
Transaction                            :    GBB
Valuation / acct modification :     /AUF
Material / valuation class        :     (Finished Product) /7920
Why should we assign consumption account for valuation class 7920. Where i am doing mistake.

I had faced similar error y'day.. message that say's 'consumption account' is really misleading.. but, i think system is checking this account assignment upfront while creating the order. basically GBB/AUF assignment is required for 101 of FG/SFG material after production..
so, just assign a p&l account to VC 7920 and create the order it would be good..
Regards,
Sayujya
Edited by: Sayujya Patil on Jul 1, 2011 3:06 PM

Migo is not showing the excise tab - header level and item level

Hi,
i have created one PO with excise and i have created MIGO with only capture excise invoice, in MIGO before saving the document system is showing the excise basic, cess and higher education cess in excise tab, header level as well as item level. After saving the document, if i go to dispaly view of the MIGO document system is not showing the header level as well as item level excise amount. The tab itself is not appearing. Can any one help me on this.

Hi,
There are two kinds of statuses, system status and user status.
You can only influence System status if you execute a business transaction that changes the system status.there
are four system statuses open, In process,Released and Completed.
User status can be created as additional information to the system status in any numbers.But for this you
need to define a status profile which would further be assigned to transaction type(header status) and
item categories(item status).
The header status is independent of the item status. One exception is the status Completed.
If all items have the status Completed, the header status is also set to Completed.
For defining a status profile you need to go to
SPRO>Customer Relationship Management>Transactions>Basic settings>Status Management.
Hope this helps.
Regards
Sidd

Excise GL accounts during billing and J1iin( excise posting)

Hi,
Could any of you help me by providing the excise GL accounts which would be debited and credited during generation of billing document and at the time of excise invoice creation (J1iin posting) in Sales invoices
Thanks in advance
Uma

hii..
I. Direct billing to dealers
(a) Delivery creation VL01 Dr. Cost of Goods Sold A/c
Cr. Stock of Vehicles A/c
(b) Billing VF01 Dr. Dealer A/c
Cr. Sales - Vehicles A/c
Cr. Excise Duty Paid A/c
Cr. Sales Tax Payable A/c
(c) Excise invoice J1IIN Dr. Excise Duty Paid A/c
Cr. Excise Duty Liability A/c
Cr. Excise Duty Liability - Cess A/c
II. Stock transfer (Out)
(a) Delivery creation VL01 Dr. Stock of Vehicles (Receiving Plant) A/c
Cr. Stock of Vehicles (Sending Plant) A/c
(b) Billing VF01 Dr. Dealer A/c
Cr. Sales - Vehicles A/c
Cr. Excise Duty Recovery A/c
Cr. Sales Tax Payable A/c
(c) Excise invoice J1IIN Dr. Excise Duty Paid A/c
Cr. Excise Duty Liability A/c
Cr. Excise Duty Liability - Cess A/c
III. Branch billing to dealers
(a) Delivery creation VL01 Dr. Cost of Goods Sold A/c
Cr. Stock of Vehicles A/c
(b) Billing VF01 Dr. Dealer A/c
Cr. Sales - Vehicles A/c
Cr. Excise Duty Recovery A/c
Cr. Sales Tax Payable A/c
5 Payment of Excise Duty
(a) By utilising credit in RG23 J2IUN Dr. Excise Duty Liability A.c
Dr. Excise Duty Liability - Cess A/c
Cr. CENVAT Receivable-Input A/c
Cr. CENVAT Receivable-Capital Goods A/c
Cr. Education Cess Receivable-Capital Goods A/c
(b) By utilising PLA J2IUN Dr. Excise Duty Liability A.c
Dr. Excise Duty Liability - Cess A/c
Cr. Excise PLA A/c
(c) By payment thro' PLA
At the time of cheque issue FB60 Dr. Excise Deposit on Hold A/c
Cr. Bank A/c
On receipt of TR6 Challan J1IH Dr. Excise PLA A/c
Cr. Excise Deposit on Hold A/c
Regards,
Aakash

Client level , company code level , chart of account level

Hi experts
Pls expline me which are we define under client level , company code level and COA level
like :
1) field status variant:
2) Dunning procedure:
3) document types:
4) doc.number range:
4) posting periods variant
5) controlling area
6) account groups
7) vendor/cust master data
8) dep key
9) chart of dep area
10) like...............................
get points
Geeta

hi geeta,
ClientA Client is the highest unit within an SAP system and contains Master records and Tables. Data entered at this level are valid for all company code data and organizational structures allowing for data consistency. User access and authorizations are assigned to each client created. Users must specify which client they are working in at the point of logon to the SAP system.
A CompanyA Company is the unit to which your financial statements are created and can have one to many company codes assigned to it. A company is equivalent to your legal business organization. Consolidated financial statements are based on the companyu2019s financial statements. Companies are defined in configuration and assigned to company codes. Each company code must use the same COA( Chart of Accounts) and Fiscal Year. Also note that local currency for the company can be different.
Company CodesCompany Codes are the smallest unit within your organizational structure and is used for internal and external reporting purposes. Company Codes are not optional within SAP and are required to be defined. Financial transactions are viewed at the company code level. Company Codes can be created for any business organization whether national or international. It is recommended that once a Company Code has been defined in Configuration with all the required settings then other company codes later created should be copied from the existing company code. You can then make changes as needed. This reduces repetitive input of information that does not change from company code to company code as well as eliminate the possibility of missed data input.
Business Area Business Area is optional and is equivalent to a specific area of responsibility within your company or business segment. BA (Business Area) also allows for internal and external reporting.
Another configuration requirement for set-up in SAP are the Basic settings consisting of the following:
Chart of Accounts(COA)
Fiscal Year Variants.
Currencies
The COA(Chart of Accounts)
The COA(Chart of Accounts) lists all General Ledger accounts that are used by the organization. It is assigned in configuration to each company code and allows for daily General Ledger postings.
Fiscal Year configuration
Fiscal Year configuration is a must and can be defined to meet your companyu2019s reporting periods whether Fiscal (any period combination that is not calendar) or Calendar( Jan-Dec).
Posting Periods are defined and assigned to the Fiscal Year.
Within the periods you specify start dates and finished dates.
SAP allows for 12 posting periods along with specially defined periods that can be used for year-end financial closing.
Rohit Agrawal

Client level, chart of accounts level, company code level

Generally what are the areas under client level, chart of accounts level, company code level.
For Ex. document types are client level, number range company code level
like the above does we have any list which is falling in the above levels.

1. Generally during customising when co code data is not asked , then settings are client level.
Country, Currency, Document types, all variants of diff types, chart of accounts, etc
2. Every master is having data - General data level (client level) for use by all co codes, Co code data level(basically for accounting purposes) and so on.
These are applicable to GL, Vendor, Customer, Asset, Matlerials, etc
For particular application we have more information at another object level also- Vendor- Purchasing, Customer-Sales, materials-Plant- controlling, etc
3. Chart of accounts level assignments are done for all automatic posting definitions-which is applicable to all company codes which are using same chart of accounts.
4. In material setting- valuation can be grouping level, co code level or plant level as these are related to costing and product costing.
Hope the above will give some idea.
In the above nothing is written about CO as you have not asked-

Transfer Forecast data based on Customer information for product and plant

Hi,
This is the scenario.
Our characterstics are Product,Plant and Customers
and for 1 plant and product there may be 5 customers.
My characterstics will be
P1 L1 C1
P1 L1 C2
P1 L1 C3
P1 L1 C3
P1 L1 C4
P1 L1 C5
(P1-Product; L1 for Plant and C1,C2...are customers)
Now forecast data will be different for different customers.
I transfer demand from APO to ECC for PRoduct ,Plant and different customers.
Then in ECC how to check for different customers.
If you go to MD63 you can see for plant and product but not for customers.
This is required as we are running MRP for that product for component planning.
Thanks in Advance
Raghavendra Pai

Hi Ragvendra,
In ECC we can transfer at material and plant level only and not information of customer. As you need for MRP run may be you can explore possibility of using some badi and get customer no in requirement plan number or some other feilds.
Other option is planning with descriptive chartceristic in APO only. It is not possible to transfer demand with descriptive charcteristics to ECC.
Here you can forcast demand on customer level. Transfer it as PIR with descriptive charcteristics to PPDS where you can plan for this demand.
For information see link http://help.sap.com/saphelp_scm50/helpdata/en/c1/147a375f0dbc7fe10000009b38f8cf/frameset.htm.
If your requirement is to transfer customer information to ECC from DP in standarad it is not possible as far as I know.
Regards,
Siddharth

Pass on Material requirements to MRP areas within Plant

- We are on ECC 6.0 & have a scenario wherein material requirements from depots are passed on to respective plants according to the settings defined in the Special Procurement key in the Material Master (MRP View)
- The requirement from depots are passed on to the manufacturing plant & further down to the Plant in which MRP areas are defined, in the form of Planned Orders, if the stock is not sufficient at depot.
- For Subcontracting, we have various MRP areas within a single separate plant. The requirement is that PR that is generated for STO should be able to pass the requirement to an MRP area (after stock checking at MRP area level), (system to decide the MRP area to be selected for passing on the requirements).
- Currently the system is passing the requirements & checking the stock at plant level only.
- Stock determination rules donu2019t seem to work here.
- The opening up of the u2018Issue storage locationu2019 in STOu2019s by config: (u201CPurchase order-> - Set up Stock Transport order - > Set up Stock Transfer between storage locationsu201D) is yet to be tested.
- But in that case, only a single MRP area is defined for the material & therefore the requirements may flow directly to that particular MRP area. In case of Multiple MRP areas being defined for a single material, how can we ensure that the system determines a stock checking at one particular MRP area & pass on the requirements to it.
Seeking guidance as to how this issue can be resolved.
Precisely,
REQ.FRM>FLOW TO>AS (MRP element)
Depot>Plant 1>Planned order (PlOrd)
Plant 1>Plant 2>Material reservation (MtlRes)
Plant 2>MRP area of Plant 2>Transfer reservation (TrnRes)

dear colleague,
Please check the following info that can be useful:
1) Note 358936 is relevant for MRP areas of type storage location and
   not for Subcontractor MRP areas (which you would be knowing).
2) Secondly this note was created as an advance development and not
   for any particular customer problem. It was also feasible to
   develop this functionality with a small change.
3) The feature of procurement with Schedule lines for components
   in subcontractor MRP areas is not available in the standard SAP
   suite and there are no plans to develop this in the near future.
   This feature would be an advance development.
best regards

APO DP: Disaggregation to product&plant level from higher levels.

Hi.
We do demand planning on groups of products and for country/region in general, we have around 48.000 CVC's in our current setup. It works very well.
A new situation has arisen where we need to have the forecast split down to product and plant level.
As is we simply don't have the information at this level of granularity.
I don't see how we can add for instance product to our setup, we have around 20.000 products so the number of CVC's in DP would become massive if we did this.
I was thinking that perhaps something could be done by exporting the relevant key figures to a new DP setup with fewer characteristics (to keep the number of CVC's down) via some infocubes, perhaps some disaggregation could be done via some tables and the BW update rules. This still leaves the issue of how to get the figures properly disaggregated to plant and product though.
Does anyone have experiences on how to get the figures split to lower levels from DP when you're planning on a higher level?

Simon,
One approach as you mentioned can be creating Z Table where in you set up disaggregation proportion from product group level to product level or product location level.
Product Group X 100 Product A@loc1 10
Product B@loc1 90
Download your planning area data into infocube C and then use BW routines to convert the data from group in infocube C to lower level refereing Z Table....into another infocube..
SAP also provides such standard functionality of spliting the aggregate Demand plan to detailed level
SNP plan..through functionality like location slit or product split.
Essential you will be using same concept in yor BW solution or you may also want to consider the
release your DP to SNP planning area its as solution of diaggregation of data to lower level.
Regards,
Manish

Ristricting product at plant level -?

Hi friends-
plant A currently sels product xxx and Plant B will begin selling the same product xxx starting December 1. How do you restrict plant B from creating an order with the product xxx until december 1?
do I need to do remove plant from material master -?
what is the Transaction?
Or
Do ineed to do some where else -?
Thanks
Prasad

Here are a couple of options...
Use First Product Offer Date to have requested date > the launch date. It won't restrict order entry, but it will restrict when the customer gets the product.
or
For the plant you don't want to start selling out of change the lifecycle to something not currently being used (Developing product maybe?)
Use a listing exclusion (VB01) to restrict that lifecycle product from the sales documents types your customer uses.
When you're ready to sell the product change the lifecycle on the material
Either should work.
Cheers

In CIN excise accounting is happening.

Hi Team,
Excise invoice (Excise duty) condition accounting must not be posted for export sales. And Excise duty conditions it is marked as statistical and account determination in SD is not happening which is fine.,
But in CIN , excise accounting happens.
Please advise where to look ?
Appreciate if you can reply at the earliest.
Regards
Sits

Hi
As you told as per the business process you don't want to Hit accounting . This happens in only following cases
1. Export sale (Remmember to use the Export Customer -otherwise the Export option will not be active)
2. Deemed Export (Local Customer)
3. SEZ (Local Customer)
In J1IIN , Input the billing document number and get inside the screen. Now here you can see the Excise Values are coming .
You can see it in the bottom half of the screen.
Next - Click over that utilization buttion, in the next screen again you will find the values and a PENCIL Button.
Once you click the pencil button you will see, there are multiple option which gets activated in BLUE Color.
In Case of Export the system checks the Country of the Customer should not be IN (India). If the country is not india the Export option will not get activated.
Check for this - then you don't want excise entries - mean you want the export sale to be against bond.
As you click the button the select the option against bond in blue color and SAVE- This will not hit accounting.
But if you select NO BOND option , this will generate accounting entried.
DO NOT GO BACK TO FRONT SCREEN- SAVE the document here.
This will work fine.
Thanks.................Rishi

CIN - EXCISE ACCOUNT DETERMINATION

HI CIN experts,
I need ur valuable suggestion cin excise accounts determination.
The blw is the example of account determination ;
GRPO - 25930004
OTHR - 25930004 (SAME NBR)
DLFC- 14224023
Like this the gl numbers are assigned , can we assign as per abv ?? as per understanding the Debit entries are flown frm GRPO and Cr entries frm OTHR and DLFC...
so what's the benefit of keeping same gl nbr in GRPO and OTHR???
As well, if keep diff nbr agsinst OTHR compared to GRPO and what's impact? if i do return delviey it will hit on diff gl compared to GRPO nbr, in that case how to nullify?
Jay

Hi,
Please explain in details which account are taking abt. for GRPO , OTHR and DLFC there are many accouts.
And for accounting entries. the accounts are not taken from different Excise TT. for eg all accounts whether debit or credit will be taken from same excise TT for eg GRPO. the entries whether do debit or credit are dittermine from setting
Logistics - General->India->Account Determination->Specify Excise Accounts per Excise Transaction
here u give the accouting entries to be created and which gl accounts are pick from the Logistics - General->India->Account Determination->Specify G/L Accounts per Excise Transaction.
so check this setting.
eg for account entries..
GRPO          CR Credit     CLEAR CENVAT clearing account
GRPO          DR Debit     ONHOLD CENVAT on hold account
GRPO          DR Debit     RG23AED RG 23 AED account
GRPO          DR Debit     RG23AT1 RG 23 AT1 Account
GRPO          DR Debit     RG23BED RG 23 BED account
GRPO          DR Debit     RG23ECS RG 23 ECS Account
GRPO          DR Debit     RG23SED RG 23 SED account

Separate CIN (excise) GL accounts required at product level and plant level

Similar Messages

Maybe you are looking for