Export Invoice type not selecting on Deemed Export in J1iiN

Dear Expert,
When I am creating Export excise invoice I am not able to select export invoice type as deemed Export.
Please guide me
Thanks
Jitendra

Dear Jitendra, Please check if you have maintained default settings in the SPRO path- SPRO > Logistics general > Tax on goods movement > India > Business transactions > outgoing excise invoice > Maintain default excise and series groups. If the customer country is India and document currency is INR then only local and deemed options are applicable. J1IIN has the following logic. ======================================================================= *& * *& Form GET_EXCISE_INVOICE_NO *& * * Get the excise invoice number depending on local or export ** * FORM get_excise_invoice_no. DATA : object LIKE nriv-object. IF t_locexp = local . * local sales , use local number range object = 'J_1IEXCLOC'. ELSEIF exp_type = deem. * deemed sale, use local number range object = 'J_1IEXCLOC'. ELSE. ======================================================================== This means that the system is going to look for local invoice number range object for Deemed exports also (unless the currency is different than INR in billing). Please use the exit - J_1I7_REDETERMINE_INVOICE_TYPE to change the data in such a way that it picks up the export invoice number. Please note that ARE1 can still be created for Deemed exports. The system will look at the "EXPIND" field when creating ARE1 and if it is anything but blank then you will be allowed to create ARE1. This user exit calls the VBRK and VBRP tables where you can pass the customer type as F and change the excise invoice type from local to exports. This exit very much serves the purpose of re-determining an excise invoice invoice type. If your ABAPer is not able to do make use of it, then please go through the note 83020 and consider this for consulting. Best Regards, Vijayendra

Similar Messages

Invoice Type not being Updated while Posting INVOIC01 - Incoming Invoice

Hello,
I am trying to Post Incoming Vendor Invoice in to SAP using INVOIC01 and IDOC_INPUT_INVOIC_MRM Function Module. I am adding values INVO for Invoice, CRMO for Credit Memo in the Field E1EDK01-BSART to Post the Invoice with different Invoice Types. However, the Invoice for the PO gets Posted only as Invoice, no matter what I populate in the Segment Field E1EDK01-BSART. What could be the issue? Please let me know.
Thank You,
Venkata Phani Prasad K.

This issue has been Resolved. A Sub routine MRM_DOCUMENT_COMPLETE is called in the Function Module IDOC_INPUT_INVOIC_MRM in which the value of the USING Parameter MRM_RBKPV-TCODE is being hard coded to MR1M. Since I am using a Z-Version of this Function Module, I've changed the value of the above field to MIRO after the Subroutine call which solved the issue.
MRM_RBKPV-TCODE = 'MIRO'.
The Values to be Passed to the Field BSART in the Segment E1EDK01 are
E1EDK01-BSART = 'INVL' - For Invoice
E1EDK01-BSART = 'CRME' - For Credit Memo
Thanks,
Venkata Phani Prasad K

In J1IIN the excise invoice type is not getting changed to BOND for Export

Hi Experts,
In ECC 6.0 I am trying to create an Excise Invoice (Export) but the system in J1IIN is not allowing me to change Excise invoice type to Bond (deemed is reflecting in Blue), some more details are as follows:
The Customer is for Country India, the currency is INR, the series group is 20 (export), the sale order is of Export, the customer pricing proc in the customer master is same as what we select for other exports customers.
I have checked the configuration in IMG---LOGISTICS GENERAL--TAX ON GOODS MOVEMENTS-INDIA---BUSINESS TRANSACTIONS-OUT GOING EXCISE INVOICE---MAINTAIN DEFAULT EXCISE GROUPS AND SERIES GROUPS, the EXPORT column is blank.
Please advice as to how I will be able to get the export under bond in Excise Invoice type
Thank you,
Sagar R K

Hi Sagar..
Please note that in order to change the excise invoice type to Bond, System has to meet the below to requirement.
1. Currency should be foreign ( I mean other than local currency, In case of India currency is INR) OR
2. Ship to Party should be outside the country.
By going through your comments, I understand that what ever excise invoice type is reflected in the excise invoice i.e,Deemed is correct only.
If you want to treat this is as export then check the above mentioned two points..
Thand and Regards
Muralidhar Shetty

ARE1 creation error - "excise Invoice is not meant for Exports"

Hello Experts
We are working on ECC 6.0.
We were so far dealing with domestic sales and now have to start with exports (ARE1)
I've gone through many threads and all major configuration has been done according to J91 Block Builder. But I still have doubts.
1. While doing billing for export sales, when should excise invoice be generated. When generated then should it posted with accounting entry?
2. We've created a Running Bond & on test basis we have done billing and excise invoice (DLFC) has been generated along with billing.
But when we try to create ARE1 (J1IA101) with reference to above Official excise invoice, we get the message 4F242 ( 00090006 / 2008 excise invoice is not meant for exports). We've noticed in table J_1IEXCHDR for the above excise 90006 that the field Export Type is blank which should otherwise be B (Export under Bond). We have updated manually in the table as B to test and we are able to move ahead.
3. If we dont generate the excise with billing and try to do it in J1IIN, under utilisation even after changing the type from Local to Export only DEEMED Exports is highlighted in blue and could not be turned to BOND type.
Please suggest.
Kapil

Dear Kapil
when should excise invoice be generated
Once you generate delivery related (document type F8) proforma or commercial invoice, you should generate excise invoice
When generated then should it posted with accounting entry?
No excise entries should not be posted to accounting for export sales
excise invoice is not meant for exports
First ensure that you have a separate series group for exports.
Next in case of your Excise Invoice Type dont have any of the following, then system will throw that error
- Deemed export
- Export under bond
- Export without bond
- Export under Letter of Undertaking
Check whether the excise invoice type is generated with any of the above
thanks
G. Lakshmipathi

Export invoice type master table

Dear All,
I want master table for export invoice type of following :-
B
Export Under Bond
D
Deemed Export
N
Export Under Claim for Rebate
U
Export Under Letter of Undertaking
please check & confirm.
Thanks,
Vishwas

Hi,
All Export Types which is mentioned in the list is Predefined in SAP with Domain J_1IINDEXP
Normally each field contain Data element and if data element has certain fixed values then system show only those fixed values where ever you select export type it will show only
those Value ranges which is mentioned in domain.
Field : EXPING
Data Element : J_1IINDEXP
Domain : J_1IINDEXP
If you want to Know Go to SE11---> Domain J_1IINDEXP and click on Display.
Then Click on Value Range tab then you can see the Fix values.
Those Fix values we can't change because it is predefined by SAP.

ARE1 Error ''000005/2009 Excise Invoice is not meant for Export"

I am working on ECC6 version of sap i am trying to create the ARE1 but it give the error as '0000500001/2007 excise
invoice is not meant for export'.I am trying to debug the program i thing the sy-msg type it catch that is e thats y it
goes to other loop pls help me out .

Dear Sarthak,
I have already maintained the number range object earlier, Still i verified it and number range object is present.
The error is not due to this Number range object.
The error is still there, Pls help.
Regads,
Arunava Sahana

"Excise Invoice is not meant for Exports".

Dear All,
I am facing a problem while creating ARE1 for Export Sales.
At the time of creation (Tcode - J1IA101), when i am giving the outgoing excise invoice number, in the given field, system is saying that "Excise Invoice is not meant for Exports".
Whereas I have maintained seperate Series Group for Domestic as well as Exports.I have checked No.ranges as well, where I have found that, the Outgoing Excise invoice number is also maintained in the Number range Objects for Exports.
Can anybody suggest how to resolve the issue.
Rgds,
Indrajit

1.Check the Series Group is Maintained for Domestic and Exports
2. Maintain the number range in T.Code SNUM - Object "J_1IEXCEXP"
3.Ensure that the excise invoice number you referred is created for an export billing document.
4.Then go to J1IIN, check on the utilisation screen whether invoice type has been changed from Local to the respective export excise invoice.
5. Maintain the Bond with T.code J1IBN01 respective Plant and the Value with from to date
6. Cretae the ARE 1 through T.code J11A101 check the Excise Invoice No and the Amount
7. Check the Excise duty(BED) , E cess and Hr Edu Cess value is apperaing if not you have apply the Snote .
thanks
MJP Michael Joseph

Excise invoice is not meant for exports. Message no. 4F242

Hi All
As per my Client Requirement i need to do export sales from specific Plant(Depot). which is used for only export sales.
i created STO and then i did Delivery and Billing (JEX) and created Excise invoice with refrence to Billing Doc
while Creating ARE - 1 document through T.Code J1IA101 it thronging ERROR
0020000023/2008 excise invoice is not meant for exports
Please give me u r suggestions
Thanks in Advance
Madhu

Dear Madhu,
As per your thread system is telling that invoice is not relevant for the exports so,
Please check the Excise invoice which you created is it relevant for expotrs or relevant for STO billing i.e domestic.
I hope it will help you,
Regards,
Murali.

0000000003/2007 excise invoice is not meant for exports.

WHEN IAM CREAING ARE 1 IA M GETTING THIS ERROR
0000000003/2007 excise invoice is not meant for exports.
Message no. 4F242

Hi murali,
Do you got any solution to your problem
if you got kindly inform me
cheers
bvdv

Invoice is not getting posted to accounts it is showing the export error

invoice is not getting posted to accounts, it is showing an error of foreign trade / export data. where as it is with in the country. it is maintained for the plants abroad stock transport order.

A stock transport order to a location overseas etails crossing national borders and change of legal regulations. hence you need to maintina FT data. Please check the FT data in the billing header and item and maintian them. They are simple items like customs offices meas of transport...
This will give you a green status from the red status you will initially have. Then you can post the invoice.
regds

Why am I not able to export NEF files to Photoshop from Lightroom to edit. This is new. When I right click on an image, the export to PS option is not selectable.

Why am I not able to export NEF files to Photoshop from Lightroom to edit. This is new. When I right click on an image, the export to PS option is not selectable. I've never had this happen before. I haven't used it for a few weeks, so maybe there's an update (Mac or otherwise) that's screwing things up? HELP!

I have an Edit In - Photoshop option, but not an Export - Photoshop option.
Obviously to have right-click Edit In to work, the photo you're right-clicking on needs to be selected. I assume this is not the problem, and that the photo is selected.
Mavericks 10.9.3 has a problem where the Users folder is hidden, and you need to update iTunes to fix it, but it's been a few weeks since this happened so hopefully you're up-to-date and the Users folder isn't hidden anymore.
If you can't get things to work, I'd uninstall LR and uninstall Photoshop, then install Photoshop, and update it, then install LR and update it, as a way to get any wayward security or other OS-level things reset.

Iview not selected in the transport package during the export

Hello Expert,
I created a transport package to send the change I made on the iview com.sap.portal.masthead to QA system.
I added correctly the iview to the transport package but when I clicked on the button EXPORT to create the epa file, I found that the iview was not selected.
My change canu2019t be send to QA system.
Any idea how to fix this issue?
Thanks a lot.

Khaled,
You can not transport a standard content as it can overwrite the old version and create a new version of the content.
Refer the below link,
http://help.sap.com/saphelp_nw04s/helpdata/en/26/edee3da7138e5be10000000a114084/content.htm
You can copy a the existing iView , change the id and transport the same. Use the changed iView everywhere instead of the standard ones in this case.
Ram

Output Type not automatically determined at invoice creation

Hi Friends,
I am facing a problem that while i am generating the invoice for a particular billing document type, the output type is not automatically being determined. Instead, I have to go into the invoice in change mode (VF02) Header>Output and assign the output type to it and select the local printer and save in order to print the invoice.
I am generating the invoice for this Invoice Type/Output type for the first time.
Please suggest the possible causes.
Regards,
Pankaj

Hello Pankaj,
Suppose you are using output type RD00 for invoice print out. You have maintained the condition record for RD00 in transaction code VV31. The most important thing here is the assignment of the printer.
Suppose for output type RD00 you are maintaining the condition record for key combination - Sales Organization + Distribution Channel + Division.
At the header level you will see the Sales Organization & Distribution Channel & at the item level you will see the Division.
Sales Organization = BP01
Distribution Channel = 01
Division.............Name..........Funct.........Partner............Medium......Disp. Time.....Langu
01............... Std Division..........BP............--......................1......................3................---
Select the line item & click on Communication. Here assign the output type which you will use for the print out. Now Save the condition record.
After doing this try running one sales cycle - sales order - delivery - invoice. Save the invoice & now check in the change mode (transaction code VF02) the system will determine the output type RD00 automatically.
Note:
1. In the create mode the system will not display the output type RD00, after you have saved the invoice the output type will be determined automatically.
2. Also check if there is any requirement assigned for the key combination in the access sequence (IMG - Sales and Distribution - Basic Functions - Output Control - Output Determination - Output Determination Using the Condition Technique - Maintain Output Determination for Billing Documents - Maintain Access Sequences)
With best regards,
Allabaqsh.
(Idhasoft Ltd.)

Payment Process Request(PPR) not selecting invoice which should be eligible

I am R12 (12.1.2), DB-11.2.0.1, Solaris 64 Bit.
The PPR process is not auto selecting some of the invoices for payment which should be eligible for selection. It was working fine before and stopped working now for some invoices.
We have seen this happening in the past also, and sometime the invoices start showing again with no particular changes.
I followed the first 12 step of the document "952763.1", but no luck.
If I go to PPR, the invoices are automatically going in tables AP_UNSELECTED_INVOICES_ALL. I mean, without unselecting them, they are automatically inserted into that table on each try.
Edited by: 985596 on Feb 1, 2013 8:31 AM

Hi,
Below are the reasons for PPR are not selecting the invoices.
1. The invoice should not be selected by any other PPR
Action: Using the aplist, confirm the checkrun_id is null in ap_payment_schedules_all.
2. The payment schedule's relevant date should be between the PPR's Pay From and Pay Through dates. The relevant date for selection can be either a discount date or the due date
(a) If the due date is between the pay from and pay through dates, the payment schedule will be eligible for selection regardless of the discount date.
Action: Find the due_date in ap_payment_schedules_all.
Find the pay_from_date and pay_thru_date in ap_inv_selection_criteria_all.
If the pay_from_date is null, just confirm the due_date is less than or equal to the pay_thru_date.
If the pay_from_date is not null, confirm the due_date is greater than or equal to the pay_from_date and the due_date is less than or equal to the pay_thru_date.
If this test passes, skip to Step 3.
(b) If the due_date doesn't fall within the parameters, we must rely on the discount date(s). However, this is only available when pay_only_when_due_flag is not Y
Action: Check the pay_only_when_due_flag in ap_inv_selection_criteria_all.
If this is Y, the payment schedule did not fall within the required date parameters and was not selected for that reason.
If it is null or N, continue to the next step.
(c) Determine the relevant discount date.
Action: Confirm the pay_date_basis_lookup_code in ap_supplier_sites_all is discount.
If not, the invoice won't be selected.
See if the always_take_disc_flag in ap_supplier_sites_all is Y.
If yes, then the relevant date is the discount_date from ap_payment_schedules_all.
If no, then find the check_date from ap_inv_selection_criteria_all.
Make the following comparisons and take the date from the first one that is true.
If the check_date is on or before discount date, take the discount date.
If the check_date is on or before the second discount date, take the second discount date.
If the check_date is on or before the third discount date, take the third discount date.
If none of the above is true, the invoice will not be selected.
(d) Confirm the relevant discount date is within the date parameters.
If the always_take_disc_flag is Y, the discount date from Step (c) must be between the pay_from_date and the pay_thru_date, inclusive.
If the always_take_disc_flag is Y and the pay_from_date is null, the discount date from Step (c) just has to be on or before the pay_thru_date.
If the always_take_disc_flag is N, the discount date from Step (c) must be between the check date and the pay_thru_date, inclusive.
3. The payment schedule cannot be fully paid
Action: Confirm the payment_status_flag in ap_payment_schedules_all is N or P
Also confirm the payment_status_flag in ap_invoices_all is N or P
4. The invoice cannot be subject to forced revalidation
Action: Confirm the force_revalidation_flag in ap_invoices_all is N or Null.
5. The payment schedule's payment priority must be between the Payment Priority High and Payment Priority Low parameters designated for the PPR
Action: Find the payment_priority from ap_payment_schedules_all.
Null counts as 99.
Confirm this is between the hi_payment_priority and low_payment_priority, inclusive, from ap_inv_selection_criteria_all.
6. Cancelled invoices will not be selected
Action: Confirm the cancelled_date is null in ap_invoices_all.
7. There cannot be a hold on the payment schedule
Action: Confirm the hold_flag in ap_payment_schedules_all is null or N.
8. A supplier site level hold will prevent payment schedule selection
Action: Confirm the hold_all_payments_flag in ap_supplier_sites_all is null or N.
9. For Payment Request invoices there must be a corresponding record in hz_party_sites
Action: If the invoice_type_lookup_code in ap_invoices_all is PAYMENT REQUEST, and the party_site_id from ap_invoices_all is not null, it must match to a party_site_id from hz_party_sites.
10. Fv_econ_benf_disc.ebd_check must return Y for this invoice
This is a federal function that determines whether it is economically beneficial to pay the invoice now. If Federal is not installed, this will always return Y.
Action: Run the following to check for federal installs
set serveroutput on
begin
mo_global.set_policy_context('S',&org_id_from_invoice);
if (FV_INSTALL.ENABLED) then
dbms_output.put_line('Enabled');
else
dbms_output.put_line('Not Enabled');
end if;
end;
If this returns Not Enabled, continue to the next step. If it returns Enabled, you may need to check the federal rates setup for determining economically beneficial payments.
11. If the user specified an Invoice Batch Name, the invoice must be in that batch
Action: If invoice_batch_id is populated in ap_inv_selection_criteria_all, confirm the same invoice_batch_id is populated in ap_invoices_all.
12. If the user specified the Payee the invoice must be from that payee
Action: If the vendor_id is populated in ap_inv_selection_criteria_all, confirm the same vendor_id is populated in ap_invoices_all.
If the party_id is populated in ap_inv_selection_criteria_all, confirm the same party_id is populated in ap_invoices_all.
13. If the user specified an exchange rate type, it must not conflict with the exchange rate type on the invoice
Action: If an IS_USER inv_exchange_rate_type is populated in ap_inv_selection_criteria_all, confirm the exchange_rate_type on the invoice is also User.
If an IS_NOT_USER inv_exchange_rate_type is populated in ap_inv_selection_criteria_all, confirm the exchange_rate_type on the invoice is either null or a non user type.
14. If the user specified a payment method, it must match the payment method on the payment schedule
Action: If the payment_method_code is populated in ap_inv_selection_criteria_all, confirm the same payment_method_code is populated in ap_payment_schedules_all.
15. If the user specified a vendor type, it must match the vendor type of the invoice's supplier
Action: If the vendor_type_lookup_code is populated in ap_inv_selection_criteria_all, confirm the same vendor_type_lookup_code is populated in ap_suppliers.
16. If any legal entities were specified, the invoice must be in one of those legal entities
Action: If there are any rows in ap_le_group for this checkrun_id, the legal_entity_id in ap_invoices_all must match the legal_entity_id from one of those rows.
17. If any operating units were specified, the invoice must be in one of those operating units
Action: If there are any rows in ap_ou_group for this checkrun_id, the org_id in ap_invoices_all must match the org_id from one of those rows.
18. If any currencies were specified, the invoice's payment currency must match one of them
Action: If there are any rows in ap_currency_group for this checkrun_id, the payment_currency_code in ap_invoices_all must match the currency_code from one of those rows.
19. If any pay groups were specified, the invoice's pay group must match one of them
Action: If there are any rows in ap_pay_group for this checkrun_id, the pay_group_lookup_code in ap_invoices_all must match the vendor_pay_group from one of those rows.
20. For zero-amount invoices, the user must have checked the Include Zero Amount checkbox
Action: If the amount_remaining in ap_payment_schedules_all is 0, confirm the zero_invoices_allowed value in ap_inv_selection_criteria_all is Y.
21. Unapproved invoices will not be selected
Action: Confirm the wfapproval_status in ap_invoices_all and the wfapproval_status on each row in ap_invoice_lines_all is either APPROVED, MANUALLY APPROVED or NOT REQUIRED.
24. An invoice with holds will not be selected for payment
Action: Confirm there are no rows in ap_holds_all where release_lookup_code is null.
25. The invoice must be fully validated. A different query is executed based on whether purchase encumbrances are used for any of the included orgs
Action: Determine the value of the purch_encumbrance_flag in financials_system_parameters.
A. If the purch_encumbrance_flag is null or N, confirm none of the rows in ap_invoice_distributions_all have a match_status_flag of N or S.
B. If the purch_encumbrance_flag is Y, confirm none of the rows in ap_invoice_distributions_all have a match_status_flag of N, S or T.
26. Invoices without distributions will not get selected
Action: Confirm there are rows in ap_invoice_distributions_all.
27. For customers using CCR (a Federal functionality) the Invoice Supplier should not be CCR Expired
Action: See the statement on step 10 to determine if Federal is installed. If it is installed confirm there is not a row in FV_TPP_ASSIGNMENTS_V where the beneficiary_party_id and beneficiary_party_site_id match the party_id and party_site_id from ap_invoices_all and the fv_tpp_pay_flag equals N.
Regards,
Raju.

Discount condition type not appearing in sales order but in invoice

Hi,
I have two discount condition types (MPDI,ZSDI) in my pricing procedure,at the time of sales order creation one discount condition is not appearing.
On analyzing the condition type MPDI,system throws message "Access not been executed due to previous access",what would be the reason.
In the billing ,i could see the condition type appearing.I have checked this,but i could not understand why it is happening.Even the condition catergory of condition is empty not L.
Also please find the screen shots below,
Pradeep

Pradeep,
Am sure user might have deleted the condition type in sales order, the same condition type woudl have entered manually in invoice.
Please check my testing, i have done the same entered ZA09 manually and after saving have deleted again in sales order, after dilivery and when i created invoice here i have entered manually the same condition type.
So in your case also the same thing could have happend, check the change log and also in invoce condtion tab check the condtion type in analysis ( Invoice analysis not order). so that you can udnerstand whether it was entered manully or not.
On analyzing the condition type MPDI,system throws message "Access not been executed due to previous access",what would be the reason.
This is because in the condtion tyoe the abvoe key combiantion was found with records hence the below key combition was ignored. this you observe in your screen shot with with 5.00
So my guess is the condtion records was deleted in sales order.
thanks,
srinu.

Export Invoice type not selecting on Deemed Export in J1iiN

Similar Messages

Maybe you are looking for