Max permitted number of internal tax items reached
Experts,
I am trying to do a MIRO (IR) on a PO with 693 line items and I am getting an error saying " Maximum permitted number of internal tax items reached". The Tax Code on the PO is I3 - AP Self Assessment Use Tax and the Tax amounts on both the PO and GR are '0'.
Can someone let me know how do I overcome this error and post the IR without any issues.
All answers would be duly appreciated and rewarded with points.
Thanks,
Nandita
Because in many countries it is mandatory (tax regulatory authorities) to report those transactions even if they are non-taxable, i.e. exempt. In your case why not change the GL master record to make it a non-tax relevant GL a/c. and post?
Similar Messages
-
Error while posting miro - max permitted no of internal tax items reached
Hi expert ,
When i am posting miro i facing error like 'Maximum permitted number of internal tax items reached' .
Detailed description of error 'The maximum number of internal tax items is limited to 999' but if i entered less than that i.e. upto 600
line item then i also same error coming.
what is the solution for that.
Regards,
JyotsnaHello,
Check SAP note 1431727.
Regards,
David -
U201CMaximum permitted number of internal tax item reached"
u201CMaximum permitted number of internal tax item reached Thisi is while doing MIRO Can any one help with this!
HI
The error message FF755 you are getting it is because of the generation
of the large number of lines in table BSET on the FI that you are
receiving this error, field BSEG-BUZEI is is limited to 3 digits.
The problem you are encountering is not a error in the standard design
but rather in accordance with the standard system design. You are
creating a document which is generating more than the maximum permitted
number of internal tax items.
Please see note 643273. Read this note, it helps explain why error
occurs, you will also see in this note it is necessary to maintian your
customizing settings in table TTYPV. Please do same.
So, you have 2 standard options:
1. splitting the document
2. using the summarization functionality
Please review note 589301 and note 571928 which I have attached
for your information.
Please also review notes 117708,36353, 77161 and 370565 which I have
attached.
The system is working as designed.
Reg
Madhu M -
S_P00_07000134 : tax per business partner Vs Withholding TaX Items
In Withholding tax report S_P00_07000134, what is the difference between tax per business partner and Withholding TaX Items that we have in the section Output Control and Lists?
Hi,
These are just the output options. If you select both, the output will come for both layout.
"tax per business partner" is to sort the output based on vendor number
and "Withholding TaX Items" is for sorting the output based on withholding tax type and tax code.
Regards,
SDNer -
Maximum number of items reached in FI--help required please
Hi,
How to avoid the situation(error)
Po raised for some 300 line items.
PO consists of 3-4 header conditions and all the conditions are linked to a differrent GL account all together.
GR to be done against PO.
System fails to post the document because of the error 'max no of items reached in FI(since counter limit for accounting document lines is 999).
This is most likey to happen frequently in my requirement since the POs are often consisting of 200-300 line items and alsmost 2-3 conditions minimum.
In addition to that we have thought of going for purchase account management which means that effectively 2 more additional postings in GR.
So all in all for every line in PO there could be atleast 6-8 accounting entries getting generated at the time of MIGO or any goods movement.
This very commonly happens in Sales issues also and in Invoicng also.
I have raised this issue earlier also but could not got any concrete answer.
Many suggested to go in for split GR but how far that is advicable.
There is summerization option but I am really not getting any que out of some notes I read and some forum postings I read.
Can anyone suggest me a simple step by step approach for achieving this and basically how it works and would be helpful for me.
I repeat and request you all to help me in this.If someone has already done this then please share the knowledge.
Regards,
arjmanHi,
The issue what you mentioned is really a very painful and most complex one which we are also researching. OSS suggested a OSS note and it didn't work. Yes, as you said, we have that issue in MIRO for now....I am afraid, it would comeup in MIGO as well, then, I will have no sleep, for sure....suprizingly, OSS is working very slow on this issue to my surprize. The OSS note doesn't clearly specify what to and how to summarize. We have different issues in MIRO....one for number of tax lines exceeding 500 lines...and GR/IR lines exceeding on another end...we thought if we can't fix tax lines, at least we can work on GR/IR lines but neither one is successful....We have this issue in ECC 5 for the past 3 months...with real good expert in each functional space in the team, we couldn't fix it yet!!!
just FYI -
Maximum number of items reached in FI
Hi,
How to avoid the situation(error)
Po raised for some 300 line items.
PO consists of 3-4 header conditions and all the conditions are linked to a differrent GL account all together.
GR to be done against PO.
System fails to post the document because of the error 'max no of items reached in FI(since counter limit for accounting document lines is 999).
This is most likey to happen frequently in my requirement since the POs are often consisting of 200-300 line items and alsmost 2-3 conditions minimum.
In addition to that we have thought of going for purchase account management which means that effectively 2 more additional postings in GR.
So all in all for every line in PO there could be atleast 6-8 accounting entries getting generated at the time of MIGO or any goods movement.
This very commonly happens in Sales issues also and in Invoicng also.
I have raised this issue earlier also but could not got any concrete answer.
Many suggested to go in for split GR but how far that is advicable.
There is summerization option but I am really not getting any que out of some notes I read and some forum postings I read.
Can anyone suggest me a simple step by step approach for achieving this and basically how it works and would be helpful for me.
I repeat and request you all to help me in this.If someone has already done this then please share the knowledge.
Regards,
arjmanHi
Please check OSS note 36353. This is based on summarization/deletion of certain information like material number in FI documents, which will not impact other modules.
Hope this is useful
S Jayaram -
Hi,
we have 470 lines in delivery and "Max no of items reached in FI" comes up during post goods issue. The goods have physically left the dock. Is there a way to get around this and do a PGI. I have looked at the OSS note_0001171573_max_num_GI-Items_reached but don't know the impact on FI side. Any input or suggestion is well appreciated.
thanksHi
the error exists coz of line item has a three-digit item number in FI and therefore the system
cannot process more than 999 items for each document at the time of post goods issue
Kindly go through the OSS notes 36353 & 123223 it may help you to resolve the issue
Regards
Damu -
Message no. F5727:maximum number of items reached in FI sereen MI07
hi sap techies
Message no. F5727:maximum number of items reached in FI in screen MI07
when i try to post inventory difference in MI07(Physical difference posting) i give the difference amount and reason for movement and i try to save it.it gives me the error maximum number of items in FI reached please help
kind regards
sap fico
arman
Edited by: akausar on Oct 10, 2011 3:23 PMDear Akausar,
The error F5 727 is an error from the FI component side. This is
because FI cannot accept a posting document with more than 999 line
items.
There is a limit of (999) line items which can be posted per FI
document. This is because the line item number (BSEG-BUZEI) field
length is defined as (3) numeric positions, i.e., (999) line items.
The fact that an MM document contains X positions, doesn't
mean that the FI document will contain the same number. This is the
reason why in some occasions the error message is triggered when posting
an invoice in MM.
Please bear in mind the 'rule of the thumb' for this kind of scenarios
in which you have a large MM-Document: consider an average of 4 line
items created for each line: this is due to discounts, tax postings,etc.
Unfortunately, there are no immediate plans to expand the number of
line items beyond the current limit of (999) lines per document.
SAP's Development group is aware of this functionality change request;
however, the change is massive because BSEG is a cluster table which
is used in numerous R/3 programs. The most commonly used workarounds
are as follows:
1) Implement FI summarization (per note 36353).
2) Cancel the original billing document and split it into smaller
documents using different payment terms but actually with the
same terms.
This will avoid the (999) line item limit for FI postings.
br, Guido -
Max Menu Items Reached in Step Type Palettes
Hi,
I am seeing a greyed out text in some of my step type palettes 'Max Menu Items Reached' which is probably derived from the Resource string SEQ_MAXIMUM_MENU_ITEMS_REACHED.
What defines the maximum number of menu items in the type palettes and can it be changed.
Regards
Ray FarmerRay,
The maximum number of menu items for TestStand 2.0.1 is set to be 256. This is pre-defined and cannot be changed. The message "'Max Menu Items Reached" should be displayed once you have inserted 256 menu items.
Hope that helps!
Shannon Rariden
Applications Engineer
National Instruments -
Error Message-"Maximum number of internal sessions reached"
Hi,
In one of the User defined screen , we are getting error as
"Maximum number of internal sessions reached".
This error is not coming each & every time.This screen is used to store the values in Z-table.
This error is coming after entering 6-9 entries.
What may be the problem.
The code is as follows :
when 'save'.
INSERT zmmt001_grn_gate FROM wk_zmmt01.
INSERT zmmt002_grn_item FROM TABLE it_zmmt02.
IF sy-subrc EQ 0.
COMMIT WORK.
MESSAGE I002 WITH wk_sno.
CLEAR wk_lifnr.
CLEAR wk_ebeln.
CLEAR wk_name.
CLEAR wk_appval.
CLEAR wk_chal.
CLEAR wk_form38.
REFRESH it_temp_tc1 .
CALL TRANSACTION 'ZMMI001'.
ELSE.
ROLLBACK WORK.
MESSAGE e000 WITH text-006.
ENDIF.
Whether CALL TRANSACTION 'ZMMI001' statement having problem..
Pls give your suggestion on this.
Thanks in Advance,
Best Regards,
Pavan.Hi
I agree on the reason of the problem, too. SAP limits the number of internal sessions. By calling the transaction with <b>"CALL TRANSACTION ..."</b> statement, you keep the current transaction's program data and open a new internal session. To handle things technically, SAP forces an internal session number limit.
The solution is to use <b>"LEAVE TO TRANSACTION ..."</b> which ends the current transaction session, rolls out the relevant program and then opens the new session.
*--Serdar
[email protected] -
Calculate tax item field name in bapi .. bapi_acc_document_post
Hello Friends,
Im using Bapi>> Bapi_acc_document_post to post vendor and customer invoices, im not getting mapping field for the "calculate tax item(checkbox)" technical name is xmwst in any of the bapi strucuture.
please tell me in which bapi structure we have to pass this field so that the tax amount should get calculated automatically.
regards,
SunnyYou can try the Financial Posting Interface (FIPI).
*=======================================================================
CONSTANTS:
*=======================================================================
c_typehead TYPE stype_pi VALUE 'K',
c_typepos TYPE stype_pi VALUE 'P',
c_waers TYPE waers VALUE 'EUR',
c_blart TYPE blart VALUE 'ZN',
c_debit TYPE bschl VALUE '40',
c_credit TYPE bschl VALUE '50',
c_inddebit TYPE shkzg VALUE 'S',
c_indcredit TYPE shkzg VALUE 'H'.
*===================================================================
FORM append_ftpost
*===================================================================
USING p_stype TYPE stype_pi
p_count TYPE count_pi
p_fnam TYPE bdc_fnam
p_fval TYPE any
CHANGING pt_ftpost TYPE tt_ftpost.
DATA: ls_ftpost LIKE LINE OF pt_ftpost.
CLEAR ls_ftpost.
ls_ftpost-stype = p_stype.
ls_ftpost-count = p_count.
ls_ftpost-fnam = p_fnam.
ls_ftpost-fval = p_fval.
APPEND ls_ftpost TO pt_ftpost.
ENDFORM. "append_ftpost
*===================================================================
FORM post_document
*===================================================================
USING p_bukrs TYPE bukrs
p_gjahr TYPE gjahr
p_monat TYPE monat
p_tip TYPE zga_nomtipcont
p_saknr TYPE saknr
p_bktxt TYPE bktxt
pt_pos TYPE tt_pos.
DATA: lt_blntab TYPE tt_blntab,
lt_ftpost TYPE tt_ftpost,
lt_fttax TYPE tt_fttax,
ls_blntab LIKE LINE OF lt_blntab.
REFRESH: lt_blntab,
lt_ftpost,
lt_fttax.
CALL FUNCTION 'ENQUEUE_EZGA_NOMLOG'
EXPORTING
bukrs = p_bukrs
gjahr = p_gjahr
monat = p_monat
tipcont = p_tip
_wait = 'X'
EXCEPTIONS
foreign_lock = 1
system_failure = 2
OTHERS = 3.
IF sy-subrc IS NOT INITIAL.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
PERFORM fill_bkpf USING p_bukrs p_gjahr
p_monat p_bktxt
CHANGING lt_ftpost.
PERFORM fill_bseg USING p_saknr p_bktxt
CHANGING pt_pos lt_ftpost.
CALL FUNCTION 'POSTING_INTERFACE_START'
EXPORTING
i_function = 'C'
i_mode = 'N'
i_update = 'S'.
CALL FUNCTION 'POSTING_INTERFACE_DOCUMENT'
EXPORTING
i_tcode = 'FB01'
IMPORTING
e_msgid = sy-msgid
e_msgno = sy-msgno
e_msgty = sy-msgty
e_msgv1 = sy-msgv1
e_msgv2 = sy-msgv2
e_msgv3 = sy-msgv3
e_msgv4 = sy-msgv4
e_subrc = sy-subrc
TABLES
t_blntab = lt_blntab
t_ftpost = lt_ftpost
t_fttax = lt_fttax.
IF sy-subrc IS NOT INITIAL.
MESSAGE i021(zga_nom).
ELSE.
* Grabación en tabla de log y mensaje
READ TABLE lt_blntab INTO ls_blntab INDEX 1.
IF sy-subrc IS INITIAL AND
ls_blntab-belnr IS NOT INITIAL.
PERFORM insert_log USING p_bukrs
p_gjahr
p_monat
p_tip
ls_blntab-belnr.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ELSE.
MESSAGE ID sy-msgid TYPE 'I' NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
ENDIF.
CALL FUNCTION 'POSTING_INTERFACE_END'
EXCEPTIONS
session_not_processable = 1
OTHERS = 2.
CALL FUNCTION 'DEQUEUE_EZGA_NOMLOG'
EXPORTING
bukrs = p_bukrs
gjahr = p_gjahr
monat = p_monat
tipcont = p_tip.
ENDFORM. " post_document
*===================================================================
FORM insert_log
*===================================================================
USING p_bukrs TYPE bukrs
p_gjahr TYPE gjahr
p_monat TYPE monat
p_tip TYPE zga_nomtipcont
p_belnr TYPE belnr_d.
DATA: lv_belnr TYPE belnr_d,
ls_log TYPE zga_nomlog.
CLEAR: lv_belnr, ls_log.
ls_log-bukrs = p_bukrs.
ls_log-gjahr = p_gjahr.
ls_log-monat = p_monat.
ls_log-tipcont = p_tip.
ls_log-belnr = p_belnr.
SELECT SINGLE belnr INTO lv_belnr
FROM zga_nomlog
WHERE bukrs = p_bukrs AND
gjahr = p_gjahr AND
monat = p_monat AND
tipcont = p_tip.
IF sy-subrc IS INITIAL.
UPDATE zga_nomlog FROM ls_log.
ELSE.
INSERT zga_nomlog FROM ls_log.
ENDIF.
ENDFORM. "insert_log
*===================================================================
FORM get_posting_date
*===================================================================
USING p_gjahr TYPE gjahr
p_monat TYPE monat
CHANGING p_date TYPE dats.
DATA: lv_date TYPE dats,
lv_month TYPE tfmatage.
IF p_monat <= '12'.
CONCATENATE p_gjahr p_monat '01' INTO lv_date.
CALL FUNCTION 'FIMA_END_OF_PERIOD_DETERMINE'
EXPORTING
i_date = lv_date
i_months = '1'
IMPORTING
e_date_end_of_period = p_date.
ELSE.
CONCATENATE p_gjahr '1231' INTO p_date.
ENDIF.
ENDFORM. "get_posting_date
*======================================================================
FORM fill_bkpf
*======================================================================
USING p_bukrs TYPE bukrs
p_gjahr TYPE gjahr
p_monat TYPE monat
p_bktxt TYPE bktxt
CHANGING pt_ftpost TYPE tt_ftpost.
DATA: lv_posting_date TYPE dats,
lv_dats TYPE char10.
PERFORM get_posting_date USING p_gjahr p_monat
CHANGING lv_posting_date.
WRITE lv_posting_date TO lv_dats.
PERFORM append_ftpost USING c_typehead '1'
'BKPF-BUKRS' p_bukrs
CHANGING pt_ftpost.
PERFORM append_ftpost USING c_typehead '1'
'BKPF-MONAT' p_monat
CHANGING pt_ftpost.
PERFORM append_ftpost USING c_typehead '1'
'BKPF-BLART' c_blart
CHANGING pt_ftpost.
PERFORM append_ftpost USING c_typehead '1'
'BKPF-BUDAT' lv_dats
CHANGING pt_ftpost.
PERFORM append_ftpost USING c_typehead '1'
'BKPF-BLDAT' lv_dats
CHANGING pt_ftpost.
PERFORM append_ftpost USING c_typehead '1'
'BKPF-WAERS' c_waers
CHANGING pt_ftpost.
*PERFORM append_ftpost USING c_typehead '1'*
*'BKPF-XMWST' 'X'*
*CHANGING pt_ftpost.*
PERFORM append_ftpost USING c_typehead '1'
'BKPF-BKTXT' p_bktxt
CHANGING pt_ftpost.
PERFORM append_ftpost USING c_typehead '1'
'BKPF-XBLNR' p_bktxt+0(16)
CHANGING pt_ftpost.
ENDFORM. "fill_bkpf
*===================================================================
FORM fill_bseg
*===================================================================
USING p_saknr TYPE saknr
p_bktxt TYPE bktxt
CHANGING pt_pos TYPE tt_pos
pt_ftpost TYPE tt_ftpost.
DATA: ls_pos LIKE LINE OF pt_pos,
ls_ftpost LIKE LINE OF pt_ftpost,
lv_item TYPE buzei,
lv_wrbtr TYPE wrbtr,
lv_saknr TYPE saknr,
lv_bschl TYPE bschl,
lt_poscont TYPE TABLE OF zga_nompospost,
ls_poscont LIKE LINE OF lt_poscont,
ls_poscontaux LIKE LINE OF lt_poscont.
CLEAR: ls_pos, ls_ftpost.
REFRESH lt_poscont.
LOOP AT pt_pos INTO ls_pos.
MOVE-CORRESPONDING ls_pos TO ls_poscont.
APPEND ls_poscont TO lt_poscont.
ENDLOOP.
SORT lt_poscont BY saknr.
lv_item = '002'.
LOOP AT lt_poscont INTO ls_poscontaux.
ls_poscont = ls_poscontaux.
AT NEW saknr.
CLEAR: lv_wrbtr,
lv_saknr,
lv_bschl.
ENDAT.
CASE ls_poscont-shkzg.
WHEN c_inddebit.
lv_bschl = c_debit.
WHEN c_indcredit.
lv_bschl = c_credit.
ENDCASE.
IF ls_poscont-saknr IS INITIAL.
lv_saknr = p_saknr.
ELSE.
lv_saknr = ls_poscont-saknr.
ENDIF.
IF ls_poscont-indhkont = abap_true.
lv_wrbtr = lv_wrbtr + ls_poscont-wrbtr.
ELSE.
PERFORM fill_bsegpos USING lv_bschl lv_saknr
ls_poscont-wrbtr p_bktxt
ls_poscont-kostl ls_poscont-prctr
lv_item
CHANGING pt_ftpost.
CLEAR: lv_wrbtr,
lv_saknr,
lv_bschl.
lv_item = lv_item + 1.
ENDIF.
AT END OF saknr.
IF ls_poscont-indhkont = abap_true.
PERFORM fill_bsegpos USING lv_bschl lv_saknr
lv_wrbtr p_bktxt
ls_poscont-kostl ls_poscont-prctr
lv_item
CHANGING pt_ftpost.
lv_item = lv_item + 1.
ENDIF.
ENDAT.
ENDLOOP.
ENDFORM. "fill_bseg
*===================================================================
FORM fill_bsegpos
*===================================================================
USING p_bschl TYPE bschl
p_saknr TYPE saknr
p_wrbtr TYPE wrbtr
p_bktxt TYPE bktxt
p_kostl TYPE kostl
p_prctr TYPE prctr
p_pos TYPE buzei
CHANGING pt_ftpost TYPE tt_ftpost.
DATA: lv_wrbtrstr TYPE char16.
WRITE p_wrbtr TO lv_wrbtrstr
CURRENCY c_waers NO-SIGN.
PERFORM append_ftpost USING c_typepos p_pos
'BSEG-BSCHL' p_bschl
CHANGING pt_ftpost.
PERFORM append_ftpost USING c_typepos p_pos
'BSEG-HKONT' p_saknr
CHANGING pt_ftpost.
PERFORM append_ftpost USING c_typepos p_pos
'BSEG-WRBTR' lv_wrbtrstr
CHANGING pt_ftpost.
PERFORM append_ftpost USING c_typepos p_pos
'BSEG-SGTXT' p_bktxt
CHANGING pt_ftpost.
IF p_kostl IS NOT INITIAL.
PERFORM append_ftpost USING c_typepos p_pos
'COBL-KOSTL' p_kostl
CHANGING pt_ftpost.
ENDIF.
IF p_prctr IS NOT INITIAL.
PERFORM append_ftpost USING c_typepos p_pos
'COBL-PRCTR' p_prctr
CHANGING pt_ftpost.
ENDIF.
ENDFORM. "fill_bsegpos
Edited by: Javier Meavilla Olivas on Feb 25, 2010 1:25 PM -
Segregate internal ordered items from purch. order items for the i-pro user
We want to know if there are any Oracle i-Procurement implementations that have segregated the internally ordered items via an Order Management sales order from items ordered on a PO (purchase order). We have considered three possible paths to purse. 1) Table of Contents: this seems to not work because you can only connect a Group at the Category level not item level, 2) Multiple responsibilities one for Inventory and one for drop ship: This is not acceptable to the user. 3) Requisition Template.
We attempted to implement this by creating two i-Pro stores named Main and Inventory Only. Our design defined that these stores be associated with a catalog for each group of item. We interpreted that the "Include items without suppliers in this catalog" flag in the Catalog definition would select those items that are stockable. However, the logic behind this flag does not consider the item attributes/Sourcing Rules set at the ORG level. Our company has two Orgs named INV for inventory and DEV for our service organization. For stockable items the items are coded Inventory Sourced in the DEV item master and the sourcing assigment is linked to a sourcing rule which is internal (that is, get from INV org). The items are coded Supplier Sourced in the INV item master and the sourcing rule is a Blanket. Thus, our inventory items were not included in the the catalog even though they were sourced internally at the DEV org because of the blanket sourcing rule in the INV org.
Thank you, NedMeera,
Which version of SBO are you using 2005 or 2007?
I don't think Serial numbers can help in this scenario. There is no hard allocation or blocking possible using Serial numbers.
This is the Work around I am thinking about.
Set the items to be Batch Managed - On Every Transaction
When performing Goods Receipt, enter the Sales Order Number as the Batch Number
When creating the delivery, using SBO_SP_TransactionNotification we can easily check the Batch of the Item being selected and verify it with the BaseRef of Delivery lines to match with Sales Order number.
If the numbers don't match we can warn user with message, "The items batch reserved for Sales Order xyz"
Even if you make a mistake when entering the batch number same as Sales Order number when doing a goods receipt. It can still be traced and blocked during delivery.
Hint: The Batch table records the Goods Receipt transaction along with the BaseDocument number, Base Ref, etc
If you decide to go this route, I could help you further.
Let me know
Suda -
ML Closing via CKMLCP - Open material & Maximum FI Item reached
Hi Experts,
when i did ML closing via transaction code CKMLCP, i found some problems:
1, for some materials such as A, Multi price determination can not be completed.
2, for some materials such as B, Revaluation of consumption can not be completed.
3, for some materials such as C, Posting closing entry failed.
I don't know under which situation these error would happen (in other words, it's WHY), and how to solve them ( solutions).
and, for posting closing entry, one error message is "Maximum number of FI items reached" with message no F5 727. what is the soluton to this issue?
could you please kindly give me some hints or suggestions?
Thanks&Regards,
Felix ShiThank you sir.
Maximum Item issue was solved owe to your solution.
I still have two materials open in Revaluation of consumption section in CKMLCP. the error message is :
Material 320003277 is blocked in valuation area 7080
Message no. CKMLVNB051
Diagnosis
You are trying to revaluate consumption for material 320003277 (with movement type ). This material is blocked.
System Response
Consumption for this material will not be revaluated.
Please kindly teams help me with this issue!!!
Many thanks in advance!
Regards,
Felix Shi -
Generating Tax Invoice Number for deferred taxes (Thailand)
Hi all,
I'm implementing deferred taxes for Thailand, and am attempting to generate an internal tax invoice number for vendors during the running of the program "Transfer Deferred Taxes".
I've set up the number ranges & intervals, number groups, created a dummy document class, and activated official document numbering for document type SA, which I'm using for the transfer posting.
However, when running the program "Transfer Deferred Taxes", I'm prompted to key in a tax invoice number of my own, which means that the system is not generating the number for me. How can I get this to work?
Thanks,
DanielHi
Ideally if it is configured for SD then VBRK-XBLNR and BKPF-XBLNR would be filled with the tax invoice number which is a 16 digit number. For your F1 invoice type check the accounting document type generated. It would mostly be RV.
You need to set up this accounting document type to consume the tax invoice number range. I guess FB70 transaction would be associated with accounting document type DR which is configured to use up the tax invoice number range.
So follow these steps:
1. First check the accounting document type created for the invoice of type F1.
2. Go to SPROCross Application Component-General Application FunctionsCross-Application Document NumberingIndonesia--Document Numbering
3. Check the document class created for country ID.
4. If document class is created as I guess it has been because you can already generate the number through FB70 transactions then check if accounting document type created from F1 invoice is assigned to the document class.
I guess it is this setting which you are missing. As a result of this tax invoice number is not getting generated for SD documents.
Thanks
Indranil -
Excise Invoice number and Internal Number
Hello Friends
I have some queries ,I will be thankful to you if you could guide me, in understanding themu2026
1) When we see the document in J1IEX ,in excise invoice tab, we see two fields :Excise invoice number and Internal Number.
For Internal number we define the range in object J_1INTNUM, but how do we define range for Excise invoice number
2) Where do we maintain the relation between GRPO (Excise Transaction type) with the Excise Invoice number
3) When do we require updating of register ,is it done on daily bases, and how can we see the entries of RG23A part 1.
4) We have excise invoice number range of posted ,in process and cancel documents which is assigned to GRPO transaction type, while running J1I7 though we select last option part 1 posted and part 2 not posted, still the system shows the cancelled documents, How can I avoid the cancel documents
Thanks
Siddharth1) When we see the document in J1IEX ,in excise invoice tab, we see two fields :Excise invoice number and Internal Number.
For Internal number we define the range in object J_1INTNUM, but how do we define range for Excise invoice number
-->> Ex inv nbr will be entered based on the vendor ex invoice .. this is external nbr assignment
2) Where do we maintain the relation between GRPO (Excise Transaction type) with the Excise Invoice number
--->> there is no relation between grpo vs. ex inv nbr
3) When do we require updating of register ,is it done on daily bases, and how can we see the entries of RG23A part 1.
>> u can see in J1I7 or thru table J_1IPART1
4) We have excise invoice number range of posted ,in process and cancel documents which is assigned to GRPO transaction type, while running J1I7 though we select last option part 1 posted and part 2 not posted, still the system shows the cancelled documents, How can I avoid the cancel documents
>> wait for others answers..
Maybe you are looking for
-
Problem with utl_smtp.write_data - immediate help needed
Hi, I have a sql code that generates a .csv file and sends it as an attachment through utl_smtp. Everything works fine but the .csv file's header gets broken after certain characters..wondering why this is happening..pls help. Please find my code bel
-
Group changes when file is created in the GUI
Hello All, Here is a outline of my situation. On a 10.5 or 10.6 client machine if I go to System Prefs, Accounts and click on the "+" and change to "group" and add a new group called "video" and set the GID to 264, it will create the new group. Then
-
How can I keep my number if I have to get a micro sim to fit my 4s
I got a blackberry but just got iPhone 4s but didnt realise it took micro sim,how can I get a micro sim and keep same phone number
-
ODI update procedure does not finish
Hi all, I would like to execute some arbitrary SQL to update some rows in an intermediary table and am using a procedure to do so. It runs but never seems to complete. If I do a dummy procedure with SELECT 1 FROM Dual then it runs fine, but this one
-
Hey!! Got a quick question. Has anyone heard of something like this... When i plug my 30g video into computer start up itunes and everything is running ok, but then i go into ipod options and select the video tab, everything is grey water mark.. and