Inconsistent FI/CO line item data for up dating - (RW016)
Hi,
When we post the excise invoice (J1IEX) the error came (Inconsistent FI/CO line item data for updating.The error code is RW016.So how do i solve it.Very urgent please help.
Thanks
R.Manigandan
answered
Similar Messages
-
How to upload the line item data for the T-CODE CO12 by using LSMW
Hi ALL
i have to upload some data using the t-code CO12 by LSMW. can anybody help me where and what code i have to write to upload the multiple line-items in that.
Thanks in advance.i think this follows the rule for BDC with table control, can you please give me some example code and also the step number where i have to write the code for uploading the multiple line items.
thanks in advance ! -
Production order line item data
Hello All,
I am working on production orders co03 rite now.
I want to access the line item data for a particular order,
AUFK and AFPO are not giving the details i need,
please advise,
thanks,
GauravDear Gaurav,
U shud try the Table AUFM to get the details u r looking for.
U will get your required output.
Reward points if u feel it was helpful
Regards
Srinivasan -
What is table name in SAP R/3 for PM order line item data
Hello,
I am extracting data for PM module and Interested in PM order line item data. Table AUFK is for PM order header master data.
Is there any other table for PM order line item master data?
Thanks,
IshakHi Ishak,
The item table is AUFP.
Thanks. -
Line Items Data Source for General Ledger
Hello everybody,
I'm trying to generate a Data Source for Line Items (new General Ledger) in transaction FAGLBW03. When I generated a Total Record-Data Source, everything was done correctly. When I try to generate a Line Item-Data Source, I receive following error message: "Extractors for general ledger documents are not yet supported". I was looking for any SAP notes that would explain this issue, but I couldn't find anything.
Could you please tell me how can I generate Data Source for Line Items? Add some SP, use some another transaction, ...?
Thank you for any help
JanuleHi,
Can u tell me how did u solve that problem.
i m facing same.
/sachinkumar. -
Hello,
Currently I'm working with excel SAP interfacing. For this I am using VBA to call different BAPI functions.
I have already some interface scripts working, however I have also one which I cannot discover what I'm missing.
The VBA code is to reach BAPI_ACC_DOCUMENT_POST
My error is ---> FI/CO interface: Inconsistent FI/CO document header data for updating
So I'm appealing to you SAP bapi VBA gurus whether you have any ideas how to fix my issue.
I'm attaching below my code for you to review:
Option Explicit
' Declaration for the necessary objects
Dim objBAPICortrol, objConnection, objCreateMaterial, objReturn As Object
Dim objPRFCT, objNTXT, objDTXT As Object
Dim vLastRow, vRows As Integer
Dim objMaterial1, objMaterial2, retMess As Object
Sub Batch()
' Getting the last filled Row in Column
vLastRow = Cells(Rows.Count, "A").End(xlUp).Row
' Setting the necessary variables for R/3 connection
Set objBAPICortrol = CreateObject("SAP.functions")
Set objConnection = objBAPICortrol.Connection
objConnection.System = "SYSTEM NAME"
objConnection.Client = "Client number"
objConnection.user = "USERNAME"
objConnection.Password = "PASSWORD"
objConnection.Language = "EN"
' Establish a connection
If objConnection.logon(0, False) <> False Then
'MsgBox "Connection Established"
End If
On Error Resume Next
' Assign the Parameters
Set objCreateMaterial = objBAPICortrol.Add("BAPI_ACC_DOCUMENT_POST")
Set objMaterial = objCreateMaterial.Exports.Item("DOCUMENTHEADER")
Set objMaterial1 = objCreateMaterial.Tables.Item("ACCOUNTGL")
Set objMaterial2 = objCreateMaterial.Tables.Item("CURRENCYAMOUNT")
'Set Values
objMaterial.Value("USERNAME") = "USERNAME"
objMaterial.Value("HEADER_TXT") = "BAPITEST"
objMaterial.Value("COMP_CODE") = "0001"
objMaterial.Value("PSTNG_DATE") = "20140506"
objMaterial.Value("TRANS_DATE") = "20140506"
objMaterial.Value("DOC_DATE") = "20140506"
objMaterial.Value("FISC_YEAR") = "2014"
objMaterial.Value("DOC_TYPE") = "SA"
objMaterial.Value("REF_DOC_NO") = "BAPITEST"
objMaterial.Value("FIS_PERIOD") = "00"
objMaterial1.Rows.Add
objMaterial1.Value(1, "ITEMNO_ACC") = "1"
objMaterial1.Value(1, "GL_ACCOUNT") = "0007180000"
objMaterial1.Value(1, "ITEM_TEXT") = "BAPITEST1"
objMaterial1.Value(1, "DOC_TYPE") = "SA"
objMaterial1.Value(1, "COMP_CODE") = "0001"
objMaterial1.Value(1, "PROFIT_CTR") = "AZ1111" ---->'profit center is normally having 10CHARS but as there are letters I'm not using zeros at the beginning
objMaterial1.Value(1, "ITEMNO_ACC") = "2"
objMaterial1.Value(1, "GL_ACCOUNT") = "0007180000"
objMaterial1.Value(1, "ITEM_TEXT") = "BAPITEST1"
objMaterial1.Value(1, "DOC_TYPE") = "SA"
objMaterial1.Value(1, "COMP_CODE") = "0001"
objMaterial1.Value(1, "PROFIT_CTR") = "AZ1111"
objMaterial2.Rows.Add
objMaterial2.Value(1, "ITEMNO_ACC") = "1"
objMaterial2.Value(1, "CURRENCY") = "EUR"
objMaterial2.Value(1, "AMT_DOCCUR") = "-1.00"
objMaterial2.Value(1, "ITEMNO_ACC") = "2"
objMaterial2.Value(1, "CURRENCY") = "EUR"
objMaterial2.Value(1, "AMT_DOCCUR") = "1.00"
' Function call
objCreateMaterial.call
Set objReturn = objBAPICortrol.Add("BAPI_TRANSACTION_COMMIT")
objReturn.call
Set retMess = objCreateMaterial.Tables.Item("RETURN")
If retMess Is Nothing Then
MsgBox retMess.Value(1, "MESSAGE")
End If
' Get return parameters & display in excel
Set objReturn = objCreateMaterial.Tables("RETURN")
ActiveSheet.Cells(5, 1) = retMess.Value(2, "MESSAGE")
End Subafter some searching I've discovered that once I'm creating next line for accounting document it is not working properly.
When I debug the BAPI in SE37 after inserting new line it is asking for GL account input, however if I run it using VBA and delete the account from the code, the return message is not giving me any error that GL account is missing.
I appreciate any ideas. -
AP Line-Item Report for State Auditors
Dear Members,
I am preparing one Report named AP Line-Item Report for State Auditors and i need the following fields in my report.
Check Number PAYR-CHECT
Voucher Number BSEG-BELNR
Check Date PAYR-ZALDT
Voucher Date BKPF-BUDAT
Vendor Number LFA1-LIFNR
Vendor Name ADRC-NAME1
Vendor Street Address ADRC-STREET
Vendor City ADRC-CITY1
Vendor State ADRC-REGIO
Vendor Zip Code ADRC-POST_CODE1
General Ledger Acct No BSEG-HKONT
Purchase Order Number BSEG-EBELN
Tax Status Code BSEG-MWSKZ
Taxable Amount BSEG-HWBAS
Exempt Amount BSEG-MWSTS
Tax BSEG-MWSTS
Tax Accrued BSEG-MWSTS
Total Invoice BSEG-DMBTR
I am new to FI.So I request some one please let me know which datasources contain the above fields and which CUBE is best suited for this.
Thanks in Advance for help and quick reply is much much appreciated.
Best Regards
RC0VENDOR_ATTR - Vendor Master Data Attributes
0FI_AP_51 - Check Register Line Items
0FI_AP_4 - Accounts Payable Line Items
It should be noted, however, that this won't get you everything that you need, so you may have to create enhance one or more of these DataSources and create User Exit ABAP code to get the required data. Also, the 0FI_AP_51 DataSource isn't available if your source system isn't ECC6 EHP3 or higher. If your source system is less than that, you're going to have to create a generic DataSource for the data from the PAYR table. -
Line item data is not saving while creating a Sales order using Interactive
Hi all,
I am creating a sales order Using Interactive forms. In the form i am having Header data and line item data.I had created two structures one for Header data and one for Line item data. For entering the LINE ITEM DATA i had created a Dynamic table with Buttons ADD ROW and DELETE ROW.
User will Add the Row or Delete the Row based on the requirement.
My issue is When ever the user clicks the SUBMIT button after entering the header data and 3 line items data , Sales order has been created with only first line item and the remaining two line items are not created.
My Interactive form is like below
HEADER DATA
DOC_TYPE
SALES_ORG
DIST_CHN
DIVISION
PURCH_NO
PARTN_ROLE
PART_NO
LINE ITEM DATA
ITEM_NO MATERIAL PLANT QTY COND_TYPE COND_VALUE
ADD ROW
DELETE ROW
SUBMIT
My code for the method ONACTIONCLICK is like below
method ONACTIONCLICK .
data:
Node_Adobe type ref to If_Wd_Context_Node,
Node_Zsaleheader type ref to If_Wd_Context_Node,
Elem_Zsaleheader type ref to If_Wd_Context_Element,
Stru_Zsaleheader type If_Main=>Element_Zsaleheader,
Node_Zsaleitem type ref to If_Wd_Context_Node,
Elem_Zsaleitem type ref to If_Wd_Context_Element,
Stru_Zsaleitem type If_Main=>Element_Zsaleitem.
data: header_data type BAPISDHEAD.
data: item_wa type BAPIITEMIN.
data: item_data type table of BAPIITEMIN.
data: partner_wa type BAPIPARTNR.
data: partner_data type table of BAPIPARTNR.
data: sales_order type BAPIVBELN-VBELN.
data: Errorlog type BAPIRETURN1.
navigate from <CONTEXT> to <ADOBE> via lead selection
Node_Adobe = wd_Context->get_Child_Node( Name = IF_MAIN=>wdctx_Adobe ).
navigate from <ADOBE> to <Zsaleheader> via lead selection
Node_Zsaleheader = Node_Adobe->get_Child_Node( Name = IF_MAIN=>wdctx_Zsaleheader ).
Node_Zsaleitem = Node_Adobe->get_Child_Node( Name = IF_MAIN=>wdctx_Zsaleitem ).
get element via lead selection
Elem_Zsaleheader = Node_Zsaleheader->get_Element( ).
Elem_Zsaleitem = Node_Zsaleitem->get_Element( ).
get all declared attributes
Elem_Zsaleheader->get_Static_Attributes(
importing
Static_Attributes = Stru_Zsaleheader ).
header_data-DOC_TYPE = Stru_Zsaleheader-DOC_TYPE.
header_data-SALES_ORG = Stru_Zsaleheader-SALES_ORG.
header_data-DISTR_CHAN = Stru_Zsaleheader-DISTR_CHAN.
header_data-DIVISION = Stru_Zsaleheader-DIVISION.
header_data-PURCH_NO = Stru_Zsaleheader-PURCH_NO.
partner_wa-PARTN_ROLE = Stru_Zsaleheader-PARTN_ROLE.
partner_wa-PARTN_NUMB = Stru_Zsaleheader-PARTN_NUMB.
append partner_wa to partner_data.
Elem_Zsaleitem->get_Static_Attributes(
importing
Static_Attributes = Stru_Zsaleitem ).
item_wa-ITM_NUMBER = Stru_Zsaleitem-ITM_NUMBER.
item_wa-MATERIAL = Stru_Zsaleitem-MATERIAL.
item_wa-PLANT = Stru_Zsaleitem-PLANT.
item_wa-REQ_QTY = Stru_Zsaleitem-REQ_QTY.
item_wa-COND_TYPE = Stru_Zsaleitem-COND_TYPE.
item_wa-COND_VALUE = Stru_Zsaleitem-COND_VALUE.
append item_wa to item_data.
CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT1'
EXPORTING
ORDER_HEADER_IN = header_data
WITHOUT_COMMIT = ' '
CONVERT_PARVW_AUART = ' '
IMPORTING
SALESDOCUMENT = sales_order
SOLD_TO_PARTY =
SHIP_TO_PARTY =
BILLING_PARTY =
RETURN = errorlog
TABLES
ORDER_ITEMS_IN = item_data
ORDER_PARTNERS = partner_data
ORDER_ITEMS_OUT =
ORDER_CFGS_REF =
ORDER_CFGS_INST =
ORDER_CFGS_PART_OF =
ORDER_CFGS_VALUE =
ORDER_CCARD =
ORDER_CFGS_BLOB =
ORDER_SCHEDULE_EX =
endmethod.
PLEASE SUGGEST ME IF ANY CODE CHANGE IS REQUIRED
Thanks in advance
AjayHi,
The item data is not read because, the dynamically added rows should also reflect back to the Web Dynpro context. When the user clicks on Add Row, use the Onsubmit event to add a empty line to internal table and then bind it to the context. And if the user removes a row, remove a row from internal table and bind it back to the context.
You may refer this article.
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/802f0ed1-a17a-2c10-7db4-d515a5b047ed
Regards,
Runal -
How to delete the Cost center line item data
How to delete the cost center line item data of particular cost center and only one cost center is exisiting for that company code.
Is there any way to delete the line items in that cost center.
Can data archiving & deleting can help us..........
does it have any effect over other cost center data....
any input needed.........
regards
rajeshHi,
i found 2 reports for you:
1) CO_TOTAL_WRI - Archiving CO Totals Records
2) RKCOITW1 - Archiving CO Line Items: Write Program
from 2) is a linlk to customize archiv-parameters
-> start it with transaction se38 / sa38
A. -
Line item data does not appear on all master pages - Adobe forms
Hi Guys,
I have a problem in Adobe forms as explained below-
I have a page in the form which has, you can say, a 2 windows or subforms ( Information window/subfirm on top right corner, main on middle of the page ). The data of the main subform is a line item data of delivery. Some parts of the same data need to be printed on the Information subform also. The main subform can overflow to next pages but the information window will have only very limited data to be printed on one page itself, meaning it does not overflow.
Now the requirement is that each line item should be printed on a new page. For example if there are 2 lines items then first line item should be printed on first page. Then there will be a conditional page break and the next line item will be printed on the next page ( I have achieved this using condition page break). The information window will contain information related to corresponding line items. If the first line item data overflows in main then information window of first line item should be printed on first and 2nd page. The second line item should start printing on 3rd page and information window of 3rd page will contain data of 2nd line item.
I created 1 body page and 1 master page. I created one internal table with data of main window and information window. I put the information window on master page to make it appear on all the pages.
This solution unfortunately does not work. The issue is that in case of overflow, 1st page information window shows first line item. 2nd pages shows 2nd line item and 3rd page is blank whereas ideally 1st and 2nd page information window should show first line item and 3rd page should show 2nd line item. This means that master page and body page are not getting linked. If I create the information window on body page itself, it does not repeat on all the pages. Please provide some inputs to resolve the issue.
Thanks
AbhiHi Abhinav,
I am also trying to solve the similar issue. Need to print the internal table data in the Master page.
Have you resolved this issue. Can you Please share your solution .
Thanks
Swarna. -
Hi,
I have report against FIAR line items data(0FIAR_O03).The purpose is to report at Customer level for aged trail balance amounts(only for charge back amounts).I have the report ready and restricted document type only with CB- charge back.But the problem is,on the R/3 side for some CB accounts,there is a reference amounts like Credit memos or Customer Payments(document type DZ and DG).How can get these refrences into my report when i restrict the report only with CB.So under charge back ammount,the user should be able to see the associated Credit memos and Customer Payments as in R/3.Thanks for the help.
Ravi.Hi Revathi,
Kindly find the answers below :
1.How the table BWOM2_TIMEST will work for delta & what is the selection will happen at BKPF-CPUDT
Basically, BWOM2_TIMEST will show you the Last Time stamp for both Init and Delta..
Whenever you will do an Init load.....automatically an entry will take place in this table.....and you will see a "X" sign in the field "LAst TS"....
Also for Delta...there may be N number of entries with Update mode D....but only for the latest delta you will see a "X" sign in the field "LAst TS"....
With Financial Accounting line items that have been posted in the SAP R/3 system since the last data request, the extractors identify the following delta dataset using the time stamp in the document header (BKPF-CPUDT).
2.How the tbale will wok BWOM_SETTINGS for delta
With these settings your delta extraction uses CPU date of recording records in table in R/3 to define your security interval with at least 1 day
This means that your data is loaded until the actual day - 1.
You can check the SAP note : 485958
Regards,
Debjani.. -
Hi experts,
What is Line Item Data? Can somebody give me an example to understand better the use of Line item data from the reporting prospective?
thanks in advance
regards,
dubbuHi
I think ur question releted to LINE ITEM DIMENSION
Line Item and High Cardinality
Use
When compared to a fact table, dimensions ideally have a small cardinality. However, there is an exception to this rule. For example, there are InfoCubes in which a characteristic document is used, in which case almost every entry in the fact table is assigned to a different document. This means that the dimension (or the associated dimension table) has almost as many entries as the fact table itself. We refer here to a degenerated dimension. In BW 2.0, this was also known as a line item dimension, in which case the characteristic responsible for the high cardinality was seen as a line item. Generally, relational and multi-dimensional database systems have problems to efficiently process such dimensions. You can use the indicators line item and high cardinality to execute the following optimizations:
1. Line item: This means the dimension contains precisely one characteristic. This means that the system does not create a dimension table. Instead, the SID table of the characteristic takes on the role of dimension table. Removing the dimension table has the following advantages:
¡ When loading transaction data, no IDs are generated for the entries in the dimension table. This number range operation can compromise performance precisely in the case where a degenerated dimension is involved.
¡ A table- having a very large cardinality- is removed from the star schema. As a result, the SQL-based queries are simpler. In many cases, the database optimizer can choose better execution plans.
Nevertheless, it also has a disadvantage: A dimension marked as a line item cannot subsequently include additional characteristics. This is only possible with normal dimensions.
2. High cardinality: This means that the dimension is to have a large number of instances (that is, a high cardinality). This information is used to carry out optimizations on a physical level in depending on the database platform. Different index types are used than is normally the case. A general rule is that a dimension has a high cardinality when the number of dimension entries is at least 20% of the fact table entries. If you are unsure, do not select a dimension having high cardinality.
Note: In SAP BW 3.0, the term line item dimension from SAP BW 2.0 must a) have precisely one characteristic and b) this characteristic must have a high cardinality. Before, the term line item dimension was often only associated with a). Hence the inclusion of this property in the above. Be aware that a line item dimension has a different meaning now than in SAP BW2.0. -
CREATE SUBSTITUTION RULE FOR u0093COPYING LINE ITEM TEXT FOR LINE ITEMSu0094
Hi every body
When user post transactions in FB60 we have give the line item text, Suppose no.of lineitems are there in tht instnace my client asked to create the substitution rule to COPYING LINE ITEM TEXT FOR LINE ITEMS
pls tell me the processes how to create the substitution rule
Plz can anyboby help me out...
laxmi velagasorry,
link doesn't work:
here's the content:
you must add your rules at event 3 (complete document)
in an exit of ZGGBS000:
data htext type bseg-sgtxt.
*find
LOOP AT BOOL_DATA-BSEG INTO BSEG
WHERE bseg-sgtxt <> space.
move bseg-sgtxt to htext.
ENDLOOP.
*copy
LOOP AT BOOL_DATA-BSEG INTO BSEG
WHERE bseg-sgtxt = space.
move htext to bseg-sgtxt
*modify
MODIFY BOOL_DATA-BSEG FROM BSEG.^
ENDLOOP.
http://help.sap.com/saphelp_47x200/helpdata/en/5b/d231a843c611d182b30000e829fbfe/frameset.htm
please reward useful answers
thanks and regards
Andreas -
Schedule line item data missing in Purchase order form in ECC6.0
Hi All,
We are doing ECC6.0 upgradation project . I am trying to print Purchase order in ECC6.0 , all data is coming fine in PO except schedule line item data is missing.
Same print program and form works fine in 4.7E but schedule line item data missing in ECC6.0.
Print program is a copy of standard SAP program SAPFM06P and layoutset is a copy of MEDRUCK.
If anyone knows if there is any OSS note for the standard print program or any solution please let me know.
Thanks,
Sonali.Resolved on own.
-
MB_MIGO_BADI - Line item data inside CHECK_ITEMS method
Hi All,
I have implement MB_MIGO_BADI and i want to put a check inside the method CHECK_ITEMS where the importing parameter is line ID.
How can I get the data for the line based on the line ID inside the check_items methods, so that I can make the custom checks inside the method and populate the error message.
Please let me know how can we access the line item data inside the method CHECK_ITEMS.
Thanks and Regards,
VijayHi,
My requirement is to use BADI MB_MIGO_ITEM_BADI and restrict the creation of GR of items which have delivery date > PO Delivery date.
exact requirement is:-
Invoke Badi MB_MIGO_ITEM_BADI
Only for GR
Check EKKO-BSART =PJ where EKKO-BELNR = MSEG-EBELN
Check if the Po Line item has single or multiple delivery
a) If single
Check if MKPF-CPUDT-3 > EKPO-EEIND
Yes u2013 Create GR
No --- Give error message
b) Multiple Delivery
Check if EKET WEMNG =0
Select EKET-EINDT where EKET-WEMNG < EKET MENGE
Check EKET-EINDT < MKPF-CPUDT-3
Yes u2013 Create GR
No --- Give error message
Error Message : u201CGR Cannot be posted as Delivery date is in future u201C
Thanks
Vivek
Maybe you are looking for
-
I have a two-week old Penryn BlackBook. It came with 2GB of RAM, but I immediately ordered a 4GB upgrade kit (This one from Newegg: http://www.newegg.com/Product/Product.aspx?Item=N82E16820134560) I looked up the memory replacement guide on the Apple
-
I have researched all the postings about WebAccess and 404 errors with no resolution to my issue. I have a Windows 2003 server for use with WebAccess 7 and I am getting 404 errors when trying to access http://<server>/gw/webacc. Not sure what else to
-
Problems with the "credentials to connect" on Linux
Hi! I have installed the the FlashMediaEncoder and the FlashMediaServer on two seperate machines. The FLashMedia Server runs on a machine with OS: Linux Red Hat Enterprise. The FlashMediaEncoder on a Windows XP machine. At the Connect appears the pop
-
Strange Error, could not resolve, please help
Does any body know why would one get this error Error: File C:\GenevaSqlj\src\com\wellmanage\csm\handler\OnlineHandler.java does not contain type OnlineHandler as expected. Please adjust the class path so that the file does not appear in the unnamed
-
We have following MICCP configuration: * Two IBM AIX machines with 10gR2-RAC * ASM with raw devices * We are backing up using RMAN to ASM disk group Concerns with this configuration: ** We didn't implement tape backup ** With our limited knowledge, w