PO Collaboration : Invoice Creation Type field
Hello,
The Invoice Creation Type field in the SNC Web UI is always "Invoice Creation not allowed" irrespective of the settings to the Master Data / Transaction Data.
Given below are the settings I ve maintained
ECC System:
PO -> Item Details -> Invoice Tab:
Inv. Receipt Indicator - Checked
GR-Bsd IV - Checked / Unchecked
SNC System:
Vaildation Checks - Tried both these settings:
1. PO_INVOICE_CREATION - Active
PO_INVOICE_DATA_ASSIGN - Active
PO_INVOICE_RELATED_TO_PO_OR_ASN - Inactive
2. PO_INVOICE_CREATION - Inactive
PO_INVOICE_DATA_ASSIGN - Active
PO_INVOICE_RELATED_TO_PO_OR_ASN - Active
Infact, I am not able to see the Invoice tab itself in the PO details screen in SNC Web UI.
Note : I am using the Orders.Orders05 Idoc for sending the PO from ECC to SNC system.
Hi Bharath
Your settings are fine
Please do the following checks
If you use IDocs of type ORDERS.ORDER05, SAP SNC can instead read the data for these fields from a reference document, such as a contract, that has previously been transferred via the Core Interface (CIF).
In your PO you would have referenced a contract/agreement, Please check whether it is CIFed or not
Also before CIFING do implement these notes
1053121 & 828912
Now when you send the ORDERS idoc, The RON xml reads this data and puts in structure
<FollowUpInvoice>
<RequirementCode>01</RequirementCode>
<GoodsReceiptBasedInvoiceIndicator>TRUE</GoodsReceiptBasedInvoiceIndicator>
<CustomerSelfBillingIndicator>FALSE</CustomerSelfBillingIndicator>
<ProductTaxationCharacteristicsCode>V1</ProductTaxationCharacteristicsCode>
</FollowUpInvoice>
Irrespective, whether you create invoice for ASN or PO, the tab should be visible as Nikhil rightly mentioned
In SAP SNC , Controlling Invoice Creation for POs is done by FollowUpRequirementCode as mentioned above
Now since you are using ORDERS, you need to check you SA or Contract in Item Details Tab
the following fields need to be checked "IR" in both cases and In Header Details Field "Invoicing Party"
Also during creation of PO, make sure you dont check Unlimited Overdelivery in item delivery tab and even in your reference document.
Now after implementing above two notes reCIF and try creating PO, It will work
Please do mention whether you are able to see the above structure in your RON xml in SCM side and what details???
Best Regards
Vinod
Similar Messages
-
How to Add Values in INVOICE SUB-TYPE field at the Invoice Header Forms
Hello,
Does any body knows how could I add/modify values in the INVOICE SUB-TYPE field at the Invoice Header Forms?. This values are related to the Globalization, in this case for the Chilean Localizations.
Thanks,
Alejandro R.It gives any error or just does nothing?
Have you tried making another simple form with just one block and one or two items?
You can do this type of testing in these conditions.
Which version of forms are you using? -
Pricing date for the tax condition type should be invoice creation date
HI Folks,
As per the current design taxes conditions are determining based on the Service rendered date which is similar to the GI date and pricing type is G in copy control .
New requirement is taxes should calculate based on the Invoice creation date in the invoice.in order to acheive the solution i have customized the tax related condition type functionality "pricing date" as KOMP-ERDAT but still system calcualting the taxes based on the service rendered date and same also writing in the invoice also.
pLease help me out what need to be configured here to acheive the solution.
Regards,
Ram.Hello XYZ,
As you said the tax is calculated in Taxware system, i think taxware system is configured to calculate the taxes based on the "service rendered date". That is the reason why even you have changed the pricing date to be billing date for condition type XR1 taxware is not behaving as you expected.
You have two options.
1. Invocie creation date/ blling date is available in the structure "TAX_CAL_ITEM_IN00".If it is available in the structure ask the Taxware team to make changes in their system to consider that field value instead of the service rendered date.
2. Alternatively you can over write the filed which contains the service rendered date value with the value of billing date. This way no changes required in Taxware system. You can do that in cusotmer exit "EXIT_SAPLFYTX_USER_001" include ZXFYTU03 .
Based on my exeperince i think the consistant approach would be going with option 1 . Please revert if you need furhter information on the same
Thanks,
Srini
Edited by: srini vasarao on Jul 14, 2011 12:02 PM -
Output type not automatically triggered on invoice creation
Hi,
I want to set three output types ZCUM, ZCUR and ZPCC upon invoice creation.
I have configured it correctly. For Output types ZCUM and ZCUR i have maintained condition record in key combination "Billing Type" and for ZPCC condition record is maintained in " Sales Org /Cust. Grp. 5/Ord. reason / Bill. Type" that's the difference.
In NACZ procedure is Z10000 with requirement is 902 for all three.
Output types ZCUM and ZCUR defaulting upon initial creation. But ZPCC is not defaulting.
Can you please suggest me the solution ...
Thank You,
ArchanaHi,
As suggested by Brad, check the Output Determination analysis in Billing document .
Menu option -> Go to -> Output
Select the output type -> Select menu option Go to -> Determin. Analysis
Expand the Output type determination details of ZPCC by expnading the node in analysis.
Check whether Green button is displayed against the access sequence mentioned by you.
Regards
Vinod -
Purchase Order and Invoice creation
Hi All,
I am having some fields related to Purchase order and Invoice creation, i have to find out the tables to which tables these fields belongs to.
Below are the Header fields:
Wrbtr Tcode - MIRO,
Lfsnr Tcode - MIGO,
Evertn Tcode - Me32k,
Kbetr Tcode - Me32k,
Kschl Tcode - Mek1,
Selkz Tcode - Mek1,
Werks Tcode - Mek1,
Evart Tcode - Me31k,
Frgco Tcode - Me35k,
Sddat Tcode - Me35k,
Below are the Detail fields:
Kbetr Tcode - Mek1,
Konwa Tcode - Mek1,
Lgobe Tcode - Me21n,
Planloc Tcode - Me31k,
Datab Tcode - Mek1,
Datbi Tcode - Mek1,
Fromdate Tcode - Me31k,
Todate Tcode - Me31k,
i have to retrive all these fields from tables, so plz anybody give me exact tables to use in the select quries to retrive these fields.
Thanks in advance,
Balu.Hi,
U can get the req fields as follows:
Below are the Header fields:
1)Wrbtr Tcode - MIRO- table rseg ,field-wrbtr
give belnr (invoice no ) & BUZEI(item) if known, else, give ebeln,ebelp.
2)Lfsnr Tcode - MIGO,-table mkpf,give mblnr (mat doc no ) & ZEILE(item) field-xblnr or give ebeln,ebelp
3)Kbetr Tcode - Me32k,
table:konp or konv.
Pass ebeln to ekko, wil get KNUMV.Pass KNUMV as KNUMH in 1 of the tables- konp or konv,wil get kbetr.
4)Kschl Tcode - Mek1,
Pass ebeln,ebelp to table ekpo, get mwskx(taxcode), u will get condition type kschl from FM -FI_TAX_GET_CONDITION_TYPES.
or
table:konh or konp or konv.
Pass ebeln to ekko, wil get KNUMV.Pass KNUMV as KNUMH in 1 of the tables-konh or konp or konv, wil get kschl.
5)Werks Tcode - Mek1,-table-ekpo, field-werks(give ebeln,ebelp)
Below are the Detail fields:
1)Kbetr Tcode - Mek1,
Pass ebeln to ekko, wil get KNUMV.Pass KNUMV as KNUMH in 1 of the tables- konp or konv,wil get kbetr.
2)Konwa Tcode - Mek1,
Pass ebeln to ekko, wil get KNUMV.Pass KNUMV as KNUMH in 1 of the tables- konp or konv,wil get konwa.
3)Lgobe Tcode - Me21n,give ebeln.ebelp in table ekpo, get lgort.pass lgort to table t001l, u wil get lgobe.
4)Datab Tcode - Mek1,table-konh,field datab
Pass ebeln to ekko, wil get KNUMV.Pass KNUMV as KNUMH in - konh ,wil get datab.
5)Datbi Tcode - Mek1,table-konh,field databi
Pass ebeln to ekko, wil get KNUMV.Pass KNUMV as KNUMH in table- konh,wil get databi.
Hope its useful to u. -
User Exits for Invoice creation ,cancellation and sales return
Hi Gurus,
Pl help me it's very urgent.
I did not find any user exit invoice creation so i wrote the following code in include program
MV60AF0B_BELEG_SICHERN.
This code is to update the Z*table while saving invoice ,cancellation and sales return.
The code modification is like below
FORM BELEG_SICHERN *
Buchen Fakturabelege *
FORM BELEG_SICHERN.
READ TABLE XVBRK INDEX 1.
IF SY-SUBRC NE 0.
CALL FUNCTION 'DEQUEUE_ALL'.
MESSAGE S032.
EXIT.
ENDIF.
IF SAMH_MOD = ON.
EXPORT XKOMFK TO MEMORY ID 'SDBILLDL'.
ENDIF.
DATA: CALC_TYPE.
IF REBATE_DETERMINED = 'Y'.
CALC_TYPE = 'A'.
ELSE.
CALC_TYPE = 'I'.
ENDIF.
*{ INSERT RD1K903017 1
Work Area*********************
data : wa_xvbrk type VBRKVB.
data : wa_xvbrp type vbrpvb.
data : wa_zmigo type zmigo.
data : wa_vbrp type vbrp.
Internal table Creation*******
DATA: BEGIN OF tab_XVBRP OCCURS 100.
INCLUDE STRUCTURE VBRPVB.
DATA: END OF tab_XVBRP.
data : begin of tab_vbeln occurs 10,
vbeln type vbrk-vbeln,
knumv type vbrk-knumv,
end of tab_vbeln.
data : tab_zmigo type table of zmigo.
data : tab_vbrp type table of vbrp.
*****Data declaration*************
data : v_no_of_inv type i.
data : v_vbeln_no(10) type n.
data : v_last_inv_no(10) type n.
data : v_first_inv_no(10) type c.
data : v_tot_qty type i.
data : v_frbnr type mkpf-frbnr.
*******Ranges*********************
ranges : r_vbeln for vbrk-vbeln.
*****Populating IT****************
tab_xvbrp[] = xvbrp[].
describe table xvbrk lines v_no_of_inv.
*} INSERT
CALL FUNCTION 'RV_INVOICE_DOCUMENT_ADD'
EXPORTING
VBSK_I = VBSK
WITH_POSTING = 'A'
PREISFINDUNGSART = CALC_TYPE
IMPORTING
VBSK_E = VBSK
TABLES
XKOMFK = XKOMFK
XTHEAD = XTHEAD
XVBFS = XVBFS
XVBSS = XVBSS
XVBRK = XVBRK
XVBRP = XVBRP
XVBPA = XVBPA
XKOMV = XKOMV.
*{ INSERT RD1K903017 2
data : v_count type i,v_fkimg type i .
data : v_no_of_records(10) type n.
wa_xvbrk = xvbrk.
********Selecting the last rec no from ZMIGO
select max( sr_no ) from zmigo into v_no_of_records.
*****If Distribution channel is not ZB*********
if wa_xvbrk-vtweg ne 'ZB' and ( wa_xvbrk-fkart = 'ZRIN' or wa_xvbrk-fkart = 'ZRTE' ).
if v_no_of_inv = 1. " Process only when there is one invoice
loop at tab_xvbrp into wa_xvbrp where ( matnr ne 'CDGSTP0001' and
matnr ne 'CD-RW' and
matnr ne 'CD-RW65OHS' and
matnr ne 'CABLE' and
matnr ne 'CD-R' and
matnr ne 'CDQ80N4' and
matnr ne 'GENERAL' and
matnr ne 'NERO' and
matnr ne 'OTHERS' and
matnr ne 'SPARE PARTS' and
matnr ne 'PROMO ITEM' and
matnr ne 'PROMO-1' and
matnr ne 'PROMO-2' and
matnr ne 'PROMO-3' and
matnr ne 'PROMO-4' and
matnr ne 'PROMO-5' and
matnr ne 'PROMO-6' and
matnr ne 'PROMO-7' and
matnr ne 'PROMO-8' and
matnr ne 'PROMO-9' and
matnr ne 'PROMO-10' ).
v_fkimg = wa_xvbrp-fkimg .
v_fkimg = v_fkimg / 1000.
do v_fkimg times.
v_no_of_records = v_no_of_records + 1.
wa_zmigo-sr_no = v_no_of_records.
wa_zmigo-po_no = wa_xvbrk-vbeln.
wa_zmigo-item_no = wa_xvbrp-posnr.
wa_zmigo-mblnr = wa_xmkpf-mblnr.
wa_zmigo-doc_type = wa_xvbrk-fkart.
wa_zmigo-posting_date = wa_xvbrk-fkdat.
wa_zmigo-created_on = sy-datum.
wa_zmigo-created_time = sy-uzeit.
wa_zmigo-bill_lno = v_frbnr.
wa_zmigo-material = wa_xvbrp-matnr.
wa_zmigo-inv_no = wa_xvbrk-vbeln.
wa_zmigo-inv_item_no = wa_xvbrp-posnr.
wa_zmigo-plant = wa_xvbrp-werks.
wa_zmigo-inv_date = wa_xvbrk-fkdat.
wa_zmigo-customer = wa_xvbrk-kunag.
wa_zmigo-unit = 1.
wa_zmigo-mtype = '601'.
insert into zmigo values wa_zmigo.
enddo.
clear : wa_zmigo.
endloop.
clear : v_count,v_fkimg,wa_zmigo.
refresh tab_zmigo[].
clear v_no_of_inv.
else. "When there are Split Invoices
v_last_inv_no = wa_xvbrk-vbeln.
v_vbeln_no = v_last_inv_no - v_no_of_inv + 1.
v_first_inv_no = v_vbeln_no.
sort tab_xvbrp by vbeln.
loop at tab_xvbrp into wa_xvbrp where ( matnr ne 'CDGSTP0001' and
matnr ne 'CD-RW' and
matnr ne 'CD-RW65OHS' and
matnr ne 'CABLE' and
matnr ne 'CD-R' and
matnr ne 'CDQ80N4' and
matnr ne 'GENERAL' and
matnr ne 'NERO' and
matnr ne 'OTHERS' and
matnr ne 'SPARE PARTS' and
matnr ne 'PROMO ITEM' and
matnr ne 'PROMO-1' and
matnr ne 'PROMO-2' and
matnr ne 'PROMO-3' and
matnr ne 'PROMO-4' and
matnr ne 'PROMO-5' and
matnr ne 'PROMO-6' and
matnr ne 'PROMO-7' and
matnr ne 'PROMO-8' and
matnr ne 'PROMO-9' and
matnr ne 'PROMO-10' ).
v_fkimg = wa_xvbrp-fkimg .
v_fkimg = v_fkimg / 1000.
do v_fkimg times.
v_no_of_records = v_no_of_records + 1.
wa_zmigo-sr_no = v_no_of_records.
wa_zmigo-po_no = v_vbeln_no. "wa_vbrp-vbeln.
wa_zmigo-item_no = wa_xvbrp-posnr.
wa_zmigo-mblnr = wa_xmkpf-mblnr.
wa_zmigo-doc_type = wa_xvbrk-fkart.
wa_zmigo-posting_date = wa_xvbrk-fkdat.
wa_zmigo-created_on = sy-datum.
wa_zmigo-created_time = sy-uzeit.
wa_zmigo-bill_lno = v_frbnr.
wa_zmigo-material = wa_xvbrp-matnr.
wa_zmigo-inv_no = v_vbeln_no.
wa_zmigo-inv_item_no = wa_xvbrp-posnr.
wa_zmigo-plant = wa_xvbrp-werks.
wa_zmigo-inv_date = wa_xvbrk-fkdat.
wa_zmigo-customer = wa_xvbrk-kunag.
wa_zmigo-unit = 1.
wa_zmigo-mtype = '601'.
insert into zmigo values wa_zmigo.
enddo.
clear : wa_zmigo.
at end of vbeln.
v_vbeln_no = v_vbeln_no + 1.
endat.
clear : v_count,v_fkimg,wa_zmigo.
refresh tab_zmigo[].
endloop.
endif. "End of first 2nd IF.
clear : v_no_of_inv, v_vbeln_no.
endif.
****************Sales return************************************
if wa_xvbrk-fkart = 'ZRRE' and wa_xvbrk-vtweg ne 'ZB'.
loop at tab_xvbrp into wa_xvbrp where ( matnr ne 'CDGSTP0001' and
matnr ne 'CD-RW' and
matnr ne 'CD-RW65OHS' and
matnr ne 'CABLE' and
matnr ne 'CD-R' and
matnr ne 'CDQ80N4' and
matnr ne 'GENERAL' and
matnr ne 'NERO' and
matnr ne 'OTHERS' and
matnr ne 'SPARE PARTS' and
matnr ne 'PROMO ITEM' and
matnr ne 'PROMO-1' and
matnr ne 'PROMO-2' and
matnr ne 'PROMO-3' and
matnr ne 'PROMO-4' and
matnr ne 'PROMO-5' and
matnr ne 'PROMO-6' and
matnr ne 'PROMO-7' and
matnr ne 'PROMO-8' and
matnr ne 'PROMO-9' and
matnr ne 'PROMO-10' ).
v_fkimg = wa_xvbrp-fkimg.
v_fkimg = v_fkimg / 1000.
v_tot_qty = v_tot_qty + v_fkimg.
do v_fkimg times.
v_no_of_records = v_no_of_records + 1.
wa_zmigo-sr_no = v_no_of_records.
wa_zmigo-po_no = wa_xvbrk-vbeln.
wa_zmigo-item_no = wa_xvbrp-posnr.
wa_zmigo-doc_type = wa_xvbrk-fkart.
wa_zmigo-posting_date = wa_xvbrk-fkdat.
wa_zmigo-created_on = sy-datum.
wa_zmigo-created_time = sy-uzeit.
wa_zmigo-material = wa_xvbrp-matnr.
wa_zmigo-inv_no = wa_xvbrk-vbeln.
wa_zmigo-inv_item_no = wa_xvbrp-posnr.
wa_zmigo-plant = wa_xvbrp-werks.
wa_zmigo-inv_date = wa_xvbrk-fkdat.
wa_zmigo-customer = wa_xvbrk-kunag.
wa_zmigo-unit = 1.
wa_zmigo-mtype = '651'.
condense wa_xvbrk-xblnr.
wa_zmigo-reference = wa_xvbrk-xblnr.
********Bill of lading no**
select single bill_lno from zmigo_final into v_frbnr where inv_no = wa_xvbrk-xblnr and material = wa_xvbrp-matnr.
if sy-subrc eq 0.
wa_zmigo-bill_lno = v_frbnr.
endif.
insert into zmigo values wa_zmigo.
enddo.
clear : wa_zmigo,wa_xvbrp , v_fkimg, v_frbnr.
endloop.
endif.
*******Invoice Cancellation*****************************
if wa_xvbrk-fkart = 'ZRS1' and wa_xvbrk-vtweg ne 'ZB'.
delete tab_xvbrp[] where shkzg eq 'X'.
loop at tab_xvbrp into wa_xvbrp where ( matnr ne 'CDGSTP0001' and
matnr ne 'CD-RW' and
matnr ne 'CD-RW65OHS' and
matnr ne 'CABLE' and
matnr ne 'CD-R' and
matnr ne 'CDQ80N4' and
matnr ne 'GENERAL' and
matnr ne 'NERO' and
matnr ne 'OTHERS' and
matnr ne 'SPARE PARTS' and
matnr ne 'PROMO ITEM' and
matnr ne 'PROMO-1' and
matnr ne 'PROMO-2' and
matnr ne 'PROMO-3' and
matnr ne 'PROMO-4' and
matnr ne 'PROMO-5' and
matnr ne 'PROMO-6' and
matnr ne 'PROMO-7' and
matnr ne 'PROMO-8' and
matnr ne 'PROMO-9' and
matnr ne 'PROMO-10' ).
v_fkimg = wa_xvbrp-fkimg.
v_fkimg = v_fkimg / 1000.
v_tot_qty = v_tot_qty + v_fkimg.
do v_fkimg times.
v_no_of_records = v_no_of_records + 1.
wa_zmigo-sr_no = v_no_of_records.
wa_zmigo-po_no = wa_xvbrk-vbeln.
wa_zmigo-item_no = wa_xvbrp-posnr.
wa_zmigo-doc_type = wa_xvbrk-fkart.
wa_zmigo-posting_date = wa_xvbrk-fkdat.
wa_zmigo-created_on = sy-datum.
wa_zmigo-created_time = sy-uzeit.
wa_zmigo-material = wa_xvbrp-matnr.
wa_zmigo-inv_no = wa_xvbrk-vbeln.
wa_zmigo-inv_item_no = wa_xvbrp-posnr.
wa_zmigo-plant = wa_xvbrp-werks.
wa_zmigo-inv_date = wa_xvbrk-fkdat.
wa_zmigo-customer = wa_xvbrk-kunag.
wa_zmigo-unit = 1.
condense wa_xvbrk-zuonr.
wa_zmigo-reference = wa_xvbrk-zuonr.
wa_zmigo-mtype = '602'.
********Bill of lading no**
select single bill_lno from zmigo_final into v_frbnr where inv_no = wa_xvbrk-xblnr and material = wa_xvbrp-matnr.
if sy-subrc eq 0.
wa_zmigo-bill_lno = v_frbnr.
endif.
insert into zmigo values wa_zmigo.
enddo.
clear : wa_zmigo,wa_xvbrp , v_fkimg.
endloop.
endif.
clear : v_no_of_records.
*} INSERT
CALL FUNCTION 'STACK_RESET'.
R185D-DATALOSS = SPACE.
FOLGEAUFRUF102 = SPACE.
PERFORM SETPAR_INIT.
*{ INSERT RD1K903017 3
*} INSERT
LEAVE.
ENDFORM.
This program is working fine for single user but in production where no of people are creating the invoices from different places the data is not getting updated in table ZMIGO.
sometime populating with wrong data , partial data and sometimes no updation at all.
I have used the table locking system enqueue and dequeue FM's before n after updation but still the same
thing is happening.
What could be the reason.
Looking for help very urgent any other alternate option.Hi,
Go thru these..
Enhancement
SDVFX009 Billing doc. processing KIDONO (payment reference numbe
SDVFX010 User exit item table for the customer lines
SDVFX011 Userexit for the komkcv- and kompcv-structures
V05I0001 User exits for billing index
V05N0001 User Exits for Printing Billing Docs. using POR Procedu
V60A0001 Customer functions in the billing document
V60P0001 Data provision for additional fields for display in lis
V61A0001 Customer enhancement: Pricing
SDVFX001 User exit header line in delivery to accounting
SDVFX002 User exit for A/R line (transfer to accounting)
SDVFX003 User exit: Cash clearing (transfer to accounting)
SDVFX004 User exit: G/L line (transfer to accounting)
SDVFX008 User exit: Processing of transfer structures SD-FI
SDVFX007 User exit: Billing plan during transfer to Accounting
SDVFX006 User exit: Tax line (transfer to accounting)
SDVFX005 User exit: Reserves (transfer to accounting)
Business Add-in
SD_CIN_LV60AU02 BADI for billing
If it is helpful rewards points
Regards
Pratap.M -
Excise invoice creation for Debit Memo or Credit Memo
Dear All,
I have to create Excise Invoice J1IIN with reference to Debit Memo in Differential Invoice Senario.
When i goto J1IIN it shows Customization for Document is missing in table Billing Reference type.
How to create Excise invoice for Order related billing.Plz solve my problem.
Award Pts for useful answers.
Thx & Regards,
PankajCIN Configuration for Excise Invoices in case of RETURNs
Basically CIN is divided in to two types:
1. TAXINJ - Is a Routine Based that is used in the condition types. it will work on the logic what ever is there in the Routine.
2. TAXINN: - Is a condition Record based. Means we have to create condition records for each and every condition type that you are going to use in the Pricing Procedure.
Since Version 4.7 this TAXINN came into picture and start using this.
And one of the important points is since 4.6 c CIN comes a separate package. But after introduction of 4.7 Version, CIN is coming the SAP Package itself and even in the Customer Master Record also we will find the CIN Icon.
Basically 4 types of Pricing Procedures are used in CIN and are as follows:
1.JDEPOT - Depot Sales
2.JEXPOR - Export Sales
3.JFACT - Factory Sales
4.JSTKTR - Stock Transfer
Country Version India comes with four pricing procedures as follows:
JINFAC (Sales from manufacturing plants)
JINEXP (Export sales)
JINDEP (Sales from depots)
JINSTK (Stock transfers
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 Utilization
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 credits
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 avail 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 creates' 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
IndiaMake for Logistics General, by choosing Taxes on Goodsthe settings in Customizing Basic Excise Duties Using Condition Technique and Movements Account 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 Maintenance screen, which you can MasterExcise Rate access from the SAP Easy Access screen by choosing Indirect Taxes Excise Rate Maintenance.Data
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.
Lets 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 sub transaction types, enter the accounts for each sub transaction 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 all transactions.
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.
Logistics General 1. Go to IMG Define Structure ofData ScreenMaterial Master Configuring the Material master Screen Sequence.for each
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.
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
rewards if it helps -
PAYABLES OPEN INTERFACE INVOICE IMPORT 시 REQUIRED FIELD 정보
제품 : FIN_AP
작성날짜 : 2005-05-10
PAYABLES OPEN INTERFACE INVOICE IMPORT 시 REQUIRED FIELD 정보
==========================================================
PURPOSE
AP Open Interface Invoice Import 를 통해 Invoice 를 생성 코자 할 경우 반드시 필요한 Field 에 대한 정보이다.
Explanation
1. PO 나 Project 과 Match 하지 않는 Invoice Case
Table : AP_INVOICE_INTERFACE
==============================
Required Columns
================
-INVOICE_ID : AP_INVOICES_INTERFACE_S.NEXTVAL를 이용하여 생성됨
-INVOICE_NUM : 특정 Supplier 내에서는 unique 해야함
-VENDOR_ID/VENDOR_NUM/VENDOR_NAME : Active 하여야 하며 PO_VENDORS과 Mapping
-VENDOR_SITE_ID/VENDOR_SITE_CODE : Active 한 Site 여야 하며 PO_VENDOR_SITES table과 mapping
-INVOICE_AMOUNT : 'STANDARD' type인 경우에는 양수, 'CREDIT' type인 경우는 음수를 입력
-ORG_ID : AP_SYSTEM_PARAMETERS.ORG_ID
-SOURCE : select lookup_code from ap_lookup_codes where lookup_type='SOURCE' 중 하나
Table : AP_INVOICE_LINES_INTERFACE
==================================
Required Columns for LINE_TYPE_LOOKUP_CODE = 'ITEM'
===================================================
-INVOICE_ID : AP_INVOICES_INTERFACE.INVOICE_ID
-INVOICE_LINE_ID : AP_INVOICE_LINES_INTERFACE_S.NEXTVAL
-LINE_NUMBER : 해당 invoice 내에서 unique 해야함.
-LINE_TYPE_LOOKUP_CODE :'ITEM'
-AMOUNT
-ACCOUNTING_DATE: Optional. Defaulted from INVOICE_DATE or SYSDATE
- DIST_CODE_CONCATENATED / DIST_CODE_COMBINATION_ID
: select code_combination_id from gl_code_combinations
where account_type = 'E' and enabled_flag = 'Y'
and summary_flag = 'N'
and sysdate between nvl(start_date_active, sysdate-1)
and nvl(end_date_active, sysdate+1))
Required Columns for LINE_TYPE_LOOKUP_CODE = 'TAX'
===================================================
-INVOICE_ID : AP_INVOICES_INTERFACE.INVOICE_ID
-INVOICE_LINE_ID : AP_INVOICE_LINES_INTERFACE_S.NEXTVAL
-LINE_NUMBER : 해당 invoice 내에서 unique 해야함.
-LINE_TYPE_LOOKUP_CODE : 'TAX'
-TAX_CODE / TAX_CODE_ID : AP_TAX_CODES_ALL table에서 mapping
-AMOUNT
-ACCOUNTING_DATE : Optional. Defaulted from INVOICE_DATE or SYSDATE
-DIST_CODE_CONCATENATED or DIST_CODE_COMBINATION_ID
: select code_combination_id from gl_code_combinations
where account_type = 'E' and enabled_flag = 'Y'
and summary_flag = 'N'
and sysdate between nvl(start_date_active, sysdate-1)
and nvl(end_date_active, sysdate+1))
2. PO Matched Invoice 의 경우 Table: AP_INVOICE_INTERFACE
============================
Required Columns
================
-INVOICE_ID : AP_INVOICES_INTERFACE_S.NEXTVAL를 이용하여 생성됨
-INVOICE_NUM : 특정 Supplier 내에서는 unique 해야함
-PO_NUMBER : approved 된 PO 여야 하며 cancelled, closed 혹은 final closed 된 PO NUMBER 는 안됨. PO_HEADERS Table 과 mapping
-INVOICE_AMOUNT : 'STANDARD' type인 경우에는 양수, 'CREDIT' type인 경우는 음수를 입력
-SOURCE : select lookup_code from ap_lookup_codes where lookup_type='SOURCE'
-ORG_ID : AP_SYSTEM_PARAMETERS_ALL.ORG_ID
Table: AP_INVOICE_LINES_INTERFACE
=================================
Required Columns for PO Matched Lines
=====================================
-INVOICE_ID : AP_INVOICES_INTERFACE.INVOICE_ID
-INVOICE_LINE_ID : AP_INVOICE_LINES_INTERFACE_S.NEXTVAL
-LINE_NUMBER : 해당 invoice 내에서 unique 해야함.
-LINE_TYPE_LOOKUP_CODE : 'ITEM'
-AMOUNT : QUANTITY_INVOICED * UNIT_PRICE
If MATCH_OPTION is 'P', then populate:
-RELEASE_NUM or PO_RELEASE_ID : Blanket Release only, validated against PO_RELEASES_ALL
-PO_NUMBER or PO_HEADER_ID : Validated against PO_HEADER_ALL
-PO_LINE_NUMBER or PO_LINE_ID : Validated against PO_LINES_ALL
-PO_SHIPMENT_NUM or PO_LINE_LOCATION_ID : Validated against PO_LINE_LOCATIONS_ALL
If MATCH_OPTION is 'R', then populate:
-RECEIPT_NUMBER : RCV_SHIPMENT_HEADERS.RECEIPT_NUM
-RCV_TRANSACTION_ID or PO_LINE_LOCATION_ID : RCV_TRANSACTIONS과 Mapping
Example
Reference Documents
Note 205331.1Chandrasekar,
as i know, the main thing you should consider is, that starting from R12 you will
be able to import invoices only through the Payables Open Interface.
basically, Invoice Import is used by OA to create invoice (from expense reports or from Oracle Projects). for standard invoice import, i've ever used Payables Open Interface.
Milan
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Chandrasekara Kayamboo ([email protected]):
I would like to know which is the best way to import invoice and what are the advantages and disadvange in each.
Regards
Chandrasekar<HR></BLOCKQUOTE>
null -
Excise Invoice creation error -Billing document does not exists
Dear Experts,
I have created supplementary sales order, billing with refernece through sales order by VF01.
Now I want to create Excise Invoice but system gives error Billing Document does not exists
I have checked billing document in VBRK table & it is showing in table.
My item categroy is L2N -and set it to C
I have assigned Billing type under Outgoing excise invoice ->Assign billing type to delivery type still my excise invoice is not generating.
Pl. guide me.
Thanks
TruptiResolved my problem.
Actually in Billing item categroy if you put SD Doc. Catg. as M you can do excise invoice even if you have not created the
outbound delivery.
So cycle will be Supplementary Sales Order->VF01 with ref. to SO->J1IIN -Excise invoice creation.
Thanks to all.
Trupti. -
PO creation Date and Invoice creation Date
Hi,
Can any one help me regarding which table I can look for PO creation date and Invoice creation date. I require these fields for my reporting requirement.
Thanks in advance,
Arvind.Thanks for your response Bala.
I got the Table which I require. I have one more question on this.
Can you tell me Invoice Creation Date is RBKP-BLDAT(Document Date in Document) or RBKP-BUDAT(Posting Date in the Document) and PO creation Date is EKKO-AEDAT(Date on which the record was created) or EKKO-BEDAT(Document Date in Document).
Points already rewarded. -
Proforma Invoice creation and changes to PI
Hi,
1. Can we create a proforma invoice with reference to a quotation in standard SAP ( hope not), if so how
to configure it if not how to do the developement ( using ABAP ).
2. Can we chage a proforma invoice once it is created , can we change the quantity and price of the items.
I request you to provide me the answers for my queries.
Thanks
Venkat.Dear Venkat,
> 1. Can we create a proforma invoice with reference to a quotation in standard SAP ( hope not), if so how
> to configure it if not how to do the developement ( using ABAP ).
Here no need of ABAPer
For this requirement you can get through maintaining copy control settings between your quotation type and proforma invoice type F5.
You just copy the standard settings between OR and F5 through VTFA transaction then change the document types item categories to your document types and your item categories.
> 2. Can we chage a proforma invoice once it is created , can we change the quantity and price of the items.
Again it will depend upon the copy control settings between quotation and proforma invoice.
Billing quantity controlled by Billing quantity field at item level copy control settings.
Pricing controlled by Pricing type field at item level copy control settings.
I hope this will help you,
Regards,
Murali. -
SAP-MM CIN Error: JTAX Access sequence missing at the time of excise invoice creation in J1IS
Dear Sir,
During creation of excise invoice with ref to material doc system give a error massage JTAX access sequence is missing. Access sequence and tables are already exist in system.
1.PO
2. GR with excise capture& post here Part-I&II are genarated.
3.Invoice
4.Return delivery with reference to above goods receipt document.(122 m.type)
5. J1IS- Creating outgoing excise invoice w.r.to return delivery material document.
JTAX Access sequence missing at the time of excise invoice creation in J1ISThe same error coming while consignment stock issue to cost center.
1.Consignment Info record with excise tax code.
2.PO consignment purchase order.
3.GR with excise capture & post here Part-I&II documents are created.
Material document created but there is no accounting document.
4.While doing Consignment stock issue to cost center system generate an error message
Access sequence JTAX missing ( ) Message no. VE306" -
Order type field for PO/Document type field for PR
Hi Everybody
a) In Purchase Order creation screen (ME21)-for order type field -NB(standard order) is coming as default-How to make it blank(since we are using plantwise PO NOs)
b)In purchase requisition screation screen(ME51)also Document type-NB(standard order) is coming as default-How to make it blank(since we are using plantwise Purchase requisitions)
Thanks in advance
Joseph DavidSimple,In order of ME21/ME51,Press F4,Select Required order/requistion type,Add it to Favourite list
or else
Create a transaction variant for ME21 & ME51 using t.code SDH0.
Transaction Variant - A Step by Step Guide for Creation,Check below link,
http://wiki.sdn.sap.com/wiki/display/Snippets/TransactionVariant-AStepbyStepGuidefor+Creation
Edited by: Jeyakanthan A on Apr 2, 2010 5:42 PM -
SD - Two message category for an invoice document type
Good morning all,
I use InterCompany biling in SD with standard invoice document type 'IV' and message category 'RD04' (which enables vendor invoice creation).
My customer asks to be able to print a form for the intercompany bills.
For the non intercompany bills this is actually performed by using a specific message category.
So my question is : is there any way to have TWO message category ('RD04' + specific message for form) automatically attached to an intercompany bill (customizing, user-exit,...) ?
Best regards.
Didier GOBLET.Hi Didier
Assign the logic to the RD04 output type smartform.Then it is possible,In the smartform include the logic that it should automatically attach to the intercompany billing.
Regards
Srinath -
How the Partner Bank type field in Customer master is used ??
Hi,
When 2 bank accounts are maintained in the customer master. In the Bank type field ( Partner Bank type), I give X and Y for these 2 bank accounts.
When an invoice is raised for this customer thru Sales order, I am not able to give this partner bank type i.e X or Y in the Invoice, since the invoice is automatically created.
If I raise thru FB70, I am able to give this X or Y.
How can I use this Partner Bank type field when I raise sales invoice thru Sales order.
Can anyone help me on this as early as possible.
Regards,
G.Ameet karthikeyan.Hi Experts,
We have executed an automatic payment run in F110. Status of payment proposal and payment run are successful. Postings orders: 1 generated and 1 completed.
However, the payment method used in the payment run is incorrect. Instead of 'D', the user mistakenly inputted C. Kindly advise what is the purpose of Payment method in F110 and what will happen if the payment method used is incorrect and different from the one maintained in the vendor master.
Maybe you are looking for
-
Management Studio crashing on local SQL Server console
Unable to start the SQL Server Management Studio on the SQL Server 2012 running on Windows Server 2012 and 2012 R2 We have a number of SQL Servers deployed and in the last month all instances of the SSMS have stopped working with the following error
-
Best Practices regarding program RCOCB004
Dear Colleagues I'd like to discuss the Best Practices regarding the setup of jobs to send Process Messages In my company we have a batch job with two steps. Each steps contain one variant of program RCOCB004. The first step will send messages with S
-
How do I find out what computers are authorized to use my Store Account.
How do I find out what computers are authorized to use my Store Account? Do my iPhones count towards the 5?
-
Live migration support in ops Cenetr?
Dose Enterprise Manager Ops Center 11gr1 support the new live migration feature?
-
Correlating timecode amongst different tracks
I have four video tracks covering roughly the same extent of time (an auto race). The video sources do not all start at exactly the same time. I use quarter-pip to composite the tracks in different ways. This is where my difficulty arises. The timeco