Field BKPF-BVORG in idoc not processed

hi,
we are using idoc-type FIDCC2 for posting FI-documents.
In the idoc we have filled field BVORG. when the document is created BVORG is empty and not taken from the idoc.
does anybody have an idea ?
best regards, Martin

Correct. At least one BSEG-BUKRS (there could be multiple line items in BSEG) should be different from BKPF-BUKRS for the field BKPF-BVORG to have any value in it. When you post cross-company code document, you initiate the posting in one company code and system posts two accounting documents (assuming there are two company codes in question) - one in the initiating company code and another in the second company code in question. The value in BKPF-BVORG in the initiating company code document is the document number + initiating company code + last two digits of the fiscal year. The same value gets stored in BVORG of the header record of the second company code document as well. Please note that the BELNR in the second company code can be different from the BVORG, since that BELNR is determined from the number available in the number range of that second company code. In case of the first company code, the BELNR is same as the first 10 characters of BVORG.
The value in BVORG "links" the accounting documents in the two (or more) company codes involved in the cross-company code business transaction. There is no BVORG in BSEG.

Similar Messages

Idocs not processed automatically in BW

Dear Experts,
I have a scenario here where I extract data from source system via process chains.
The source system job completed and in BW, the outbound idocs resulted in the following Status (02).
02 Error passing data to port 1
In the infopackage message dialog, I got the message as
Could not find code page for receiving system
Errors have been reported in Business Information Warehouse during the IDoc update:
In order to resolve this, I'm manually processing the idoc using program RBDAGAIN.
Note: This issue occurs only when I trigger the infopackage via process chains.
How do I rectify this error so that the idocs are processed automatically in BW?
Br, Harish

Hi,
how much time your ecc job takes to finish job.
Is this process chain newly created one or old one?
if its old one, any changes were applied on this process chain recently?
is it showing any idoc numbers at below status bar.
if yes then try to pull them by using t code BD87.
Can you share info pack error message screen shot.
Thanks

Delete Idocs not processed

Hi, I know there are some Reports to execute which will delete Idocs. We have some Idocs that have status 51, and want to delete them.
Any ideas?

Hi,
1st way:-
IDOC Related programs
1. Archive RSEXARCA and RSEXARCB
2. Delete RSEXARCD 
3. Read archiveRSEXARCR
4. Restore RSEXARCL
2nd way:-
use FM EDI_DOCUMENT_DELETE .
pass the IDoc Number to it and delete the one which you want.
3rd way:-
use the tcode WE11 or program RSETESTD to delete an IDOC
Regards
Sudheer

Message nr 00347 by transaction FBV0 for field BKPF-REINDAT.

Hello experts,
I did a modification in the screens 0100 and 0700 of the program SAPLF040.
I added an inputfield for BKPF-REINDAT on the screen 0100 and an outputfield on the screen 0700.
When I execute transaction F-63 (register a document), I can fill in this inputfield and in the table BKPF the field REINDAT is filled in with the data.
Then I call transaction FBV0 (booking the document), and on the screen the data for BKPF-REINDAT is showed. That is good. But if I then execute the booking, I receive the message 00347 field BKPF-REINDAT (input is not allowed).
What can I do for a succesfull booking?
Kind regards,
Luc

hi all,
the solution for this problem is "Enhancement":
Program:"SAPMF05A"
Enhancement Implementation Type:"Static Enhancement Point/Section"
Enhancement Implementation Point/Section: "\PR:SAPMF05A\FO:REF_FUSSZEILE\SE:BEGIN\EI"
    LOOP AT SCREEN.
      IF screen-name = 'BKPF-REINDAT'.
        screen-input      = 1.
        screen-output     = 1.
        screen-active     = 1.
        screen-invisible = 0.
        screen-display_3d = 1.
        screen-value_help = 1.
        MODIFY SCREEN.
      ENDIF.
    ENDLOOP.
Best regards.

ALE - Idoc not getting processed automatically, instead going fine in Debug

Hello All,
I have a problem with Inbound idoc processing.
IDoc settings were made 'immediate processing' in WE20, and the process code is set correctly and the attached of Z-Fun. module to process the idocs to process code.
The error in inbound side is as 'Function module not allowed: APPL_IDOC_INPUTI' 51 status. Am sure i have to do some thing with ALE settings.
Can some body help me with correction step or sequence of steps for this ALE process.
Thanks & Regards, Jilan

Hi Jilan,
Plz follow the steps:
ALE Configuration:
     WE30 - IDOC type creation
     WE31 - Create segment
     WE81 - Message type creation
     WE82 - Link IDOC type to Message type
     SE37   - Create Inbound Function Module
     BD51 - Maintain entry for Function Module
     WE57 - Maintain
     BD57 - Link Function Module, IDOC type and Message type
     WE42 Create Inbound Process Code
     BD67 - Link Process code to Function Module
     WE20 - Create Partner Profile
     BD64 - Display Distribution Model
     WE02 - IDoc List, Display all Inbound/Outbound IDocs
     WE14 - Outbound Processing of IDocs
     BD20 - Inbound Processing of IDocs
1st Step:   Create a Segment ( WE31)
         Segment is a structure for passing data in IDoc. It actually contains the IDoc data, just like the DDIC table/structure. Segment is created with all the required fields. Then Save it. But, to actually use this Segment, you have to Release the Segment, otherwise u cant use the Segment, by menu, EDIT--> Set Release.
         Now, if you want to do some change to this Segment, u cant, unless & until u Cancel the Release, by Edit--> Cancel Release.
2nd Step:   Create IDOC Type ( WE30 )
        After creating the Segment, now we have to create the IDoc Type. IDOC Type is like an envelop of a letter, which contains the data inside it, & also some more information like address. IDoc type can be Basic Or Extended.
       Basic IDoc Type: Using some SAP existing IDOC type (ex. MATMAS) or Custom IDOC type.
       Extension IDOC Type: When we need some fields extra to an existing IDOC type, then we can extend that Basic Idoc Type by another Segment. This is called Extended idoc type
3rd Step:   Create Message Type (WE81)
     Message Type is like the Postman for sending the Letter.
4th Step:   Attach Message Type to the IDOC Type (WE82)
5th Step:   Create a Function Module (SE37)
       Write the Processing logic in a Function Module.
6th Step:   Mention the IDOC Type, i.e, 0/1/2 (BD51)
7th Step:   Assign the Message Type, IDOC Type & Function Module (WE57)
8th Step:   Create a Custom Process Code (WE42)
9th Step:   Attach the Function Module to the Process Code (BD67)
10th Step: Execute Inbound IDOC s (WE19)
Example Function Module: IDOC_INPUT_ORDERS (Standard FM to create Sales Order).
reward is useful,
regards,
Tanmay

Batch Number field in IDoc for Process Orders (message type LOIPRO01)

Hello PP experts,
Just wanted to ask if anyone of you have worked with message type LOIPRO01 (IDoc for process orders)
There is a segment-field in this IDoc E1RESBL-CHARG which has description of "Batch Number"
We tried to assign a Bath Number for an Order (using t-code COR2 --> "Goods Recpt" tab under "Receipt" section), generated an IDoc for this order, but upon checking the E1RESBL-CHARG field of the IDoc it is not populated with the Batch Number.
The material in the process order is FERT, so technically we're trying to assign a Batch Number in one of the process orders for a Finished Goods material type, so not on the component level.
Can anyone here verify:
1. is the E1RESBL-CHARG field of IDoc LOIPRO01 intended for the Product Batch Number? If Yes, how do we populate that for in the IDoc? --> Do I need to have a Reservation/Dependent Requirement for the Product for the Batch Number to be populated in the IDoc?
2. If E1RESBL-CHARG can not be populated for a Product that has no Reservation/Dependent Requirements, Do I have any option of populating this field with just the Batch Number assigned to the Process Order of that product?

Solved - LOIPRO01 IDoc does not pick up the Batch Number from AFPO table, instead from table RESB. We need batch from AFPO and just created a lookup using the Process Order Number as import param

IDOC is not processing in R/3 with status 64(Urgent)--Production issue.

Dear Folks,
Here we are implementing MIRROR sytem for data extraction in to BIW.
I had gone through the steps in PDF file(How to minimize down thime for Delta Initialization) which has given by SAP.
These are following steps I had performed in BW production
1. Using RSADMIN transcation- Assigned one user as a Debugging user.
2. With the Debugging user Created one infopackage on Purhcasing ITM datasource--
 In data selection tab, I given date as from 2002 to 2003
 In Update tab, I selected update mode as Initialize Delta process- without data transfer and Uncheck Update Data in master system immediately
 In schedule tab I selected option Start Data load immediately then Start extraction.
3.Data was requested and It was intialized properly with green status 1 from 1 Records.
4. In details tab Request, Extraction, transfer(IDOC and TRFC), Processing everything in Green color.
5.As per document I have checked in R/3 for IDOC with status 64 using transaction BD87/WE05
Problem is that IDOC is not processing in R/3 system. for that IDOC I have checked in BW montior screen using the option IDOC list in Source sytem, here also it is not showing any IDOCs.
Please let me know why BW sytem is not sending any IDOCs to source sytem.Is there any settings I could have miss in BW aswell as in R/3 system.
Note: In BW production I successfully loaded master data from R/3. aswell as I triggered infopackage-Initialization with data transfer, it is showing IDOC number properly in R/3 system.
Points is Assured for all replies.

Hi,
- check you RFC destination (normal test + authorization test)
- Check you partner profiles in WE20 and its ports WE21
- from the source system tree (RSA13) right click your source system and perform a check
- the best is to restore your source R/3 source system from BW (right click on it ans select RESTORE); you'll need to be able to log in the source system as an admin as well as opening the source system for customizing in SCC4 so that BW can recreate the correct partner parameters automatically; the best is to do that with your basis group.
hope this helps,
Olivier.

Idoc in 53 status but not processed completely. Missing authorisation error

Hi ,
Some of the ORDER Idocs are in 53 status, but the orders are not processed successfully and no PO created for these Idocs.
They got below warning message when I checked in WPER transaction code.
" Missing authorization: Purchase Order Create Purchasing Grou 110 " - "Workitems (tasks) were created for this IDoc"
This is happening once in a while for some of the idocs. Remaining all idocs are posting successfully.
These IDOCu2019s are processed via user background. Not sure why we have authorisation issues as this user has SAPALL. Any ideas?
Thanks
Deepthi.

done.

Field BKPF-STBLG not updated

While canceling the commercial as well as excise invoice the field BKPF-STBLG not updated.

Hi,
Thanks for your reply.
I did the changes to the standard sort key 018-Asset Number as per your advise and didnt get the desired outcome.
Our asset code length is 7 and sub asset length is 1
So i went to OB16 and added STBLG to the sort key 018, then system says that you can maintain only upto 18 characters.
So i have made asset number to length to 7 and sub number lengtth to 1 and STBLG length to 10.
After saving the sort key, i have assigned the same sort key to the all of my asset related GL accounts in company code data under control data tab.
Now i reversed one asset transfer transaction and checked the BKPF entry. It didnt updated either in sending company code document nor receiving company code's document.
Please advise me, if i am missing anything.
But really thankful to you for your intiation.
Thanks,
Srinu...

Sub Agreement XML import error: XML import could not process field: CONTRACT_UNIQUE_DOC_NAME

Hi All,
I am importing Sub Agreement in XML format and getting below error.
XML import could not process field: CONTRACT_UNIQUE_DOC_NAME
unsupported null bind parameter no. 0
Below is the XML.
<?xml version="1.0" encoding="UTF-8"?>
<sapesourcing xsi:noNamespaceSchemaLocation="Contracts.xsd" defaultlanguage="" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<objects>
 <object classname="contracts.Agreement">
<fields>
 <CONTRACT_UNIQUE_DOC_NAME>P-XXXX-00001</CONTRACT_UNIQUE_DOC_NAME>
 <DISPLAY_NAME>Testing Agreement Name 1 </DISPLAY_NAME>
 <CALC_METHOD>UNIT_PRICE_ENTERED</CALC_METHOD>
 <UNIQUE_DOC_NAME>S0002510</UNIQUE_DOC_NAME>
 <STATUS>In Process</STATUS>
 <COMPANY>TEST</COMPANY>
 <LOCATION>Location_114</LOCATION>
 </fields>
 </object>
</objects>
</sapesourcing>
If anyone is successful in importing Sub Agreement in XML format? also please validate the above xml structure?
Note: I am able to load Sub Agreement using CSV. But in our scenario data comes in XML format.
Thanks & Regards
Sai

Hi Gary,
I am able to load below objects in XML format without any issues. And I am using Scheduled Task of type “Data Import Monitor” to load them.
1) Project (1100)
2) Master Agreement (1004)
3) Extension Collections for Project
4) Extension Collections for Master Agreement
1) Working XML Structure for Project(1100) .
<?xml version="1.0" encoding="UTF-8"?>
<sapesourcing xsi:noNamespaceSchemaLocation="Projects.xsd" defaultlanguage="" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<objects>
 <object classname="projects.projects">
 <fields>
<UNIQUE_DOC_NAME>S0004392</UNIQUE_DOC_NAME>
<DISPLAY_NAME>Test Project</DISPLAY_NAME>
2) Working XML Structure for Master Agreement (1004) object.
<?xml version="1.0" encoding="UTF-8"?>
<sapesourcing xsi:noNamespaceSchemaLocation="Contracts.xsd" defaultlanguage="" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<objects>
<object classname="contracts.Contract">
<fields>
<UNIQUE_DOC_NAME> 00215944</UNIQUE_DOC_NAME>
<DISPLAY_NAME>TEST MA</DISPLAY_NAME>
<DOCUMENT_DESCRIPTION>Contract Desc</DOCUMENT_DESCRIPTION>
3) Working XML Structure for Extension Collections for Project(1100).
<?xml version="1.0" encoding="UTF-8"?>
<sapesourcing xsi:noNamespaceSchemaLocation="Projects.xsd" defaultlanguage="" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<objects>
<object classname="projects.projects">
<fields>
<UNIQUE_DOC_NAME> S0004392</UNIQUE_DOC_NAME>
</fields>
<collections>
<Z_DETAILS replace="true">
<object classname="extension_collections">
<fields>
<NAME>Sai</NAME>
<EMAIL>[email protected]</EMAIL>
</fields>
</object>
<object classname="extension_collections">
<fields>
<NAME>Krishna</NAME>
<EMAIL>[email protected]</EMAIL>
</fields>
</object>
</ Z_DETAILS >
</collections>
</object>
</objects>
</sapesourcing>
4) Working XML Structure for Extension Collections for Master Agreement (1004).
<?xml version="1.0" encoding="UTF-8"?>
<sapesourcing xsi:noNamespaceSchemaLocation="Contracts.xsd" defaultlanguage="" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<objects>
<object classname="contracts.Contract">
<fields>
<UNIQUE_DOC_NAME>00215944</UNIQUE_DOC_NAME>
</fields>
<collections>
<ZLINKS replace="true">
<object classname="extension_collections">
<fields>
<LINK_NAME>SAP</ LINK_NAME>
< LINK_URL> http://www.sap.com/index.html </ LINK_URL >
</fields>
</object>
<object classname="extension_collections">
<fields>
<LINK_NAME>SCN Sourcing</ LINK_NAME>
< LINK_URL>http://scn.sap.com/community/sourcing</ LINK_URL >
</fields>
</object>
</ ZLINKS >
</collections>
</object>
</objects>
</sapesourcing>
Could you please help me with the right XML Structure for Agreement( 1003)?
Regards,
Sai

Web Forms Number Field - Not processing decimals!

We have created a monster web form on a clients site. As it is, we have had to setup an API to deal with the data after its been generated by BC and modify it before sending it on to the client. The client saw no reason for fields that did not have anything entered against them to be sent through in the workflow notification - and I agreed.
Now after all these other problems have been resolved, I discover that all my "number" fields cannot process a decimal place, and they round up or down. BC have suggested I need to recreate the form and just make them all 'text strings'.
Not good enough. Its an EPIC form with over 100 fields in it. We, in good faith, read the instructions that can be found here: http://kb.worldsecuresystems.com/478/bc_478.html?bc-partner
that state "Number - a text box that must have a number entered into it". No note about NOT using decimals!
The confusing thing is, it lets you enter the decimal from the front end, even displays the web form confirmation page correctly with decimals. But when it creates a case in BC, it rounds the numbers. So its only at this late testing stage that we have discovered the issue
Does anyone have any ideas about faster ways of re-creating this entire form ?
I did submit a support ticket, and was told to switch to the old UI and then just change the type of the fields. But when we try to change a form field from 'number' to 'string' it brings up the message "WARNING: Field updated successfully but type not changed as field has associated values.". Then they said to:
Copy that specific webform change the type fields of the form and then remove the old webform and re-name this one copy with the first webform name. The copy option is available under the link I have provided to you.
However this still means we need to change *all* the fields and then get every field' s ID and insert it into the javascript. Very very time consuming
So A) everyone else be warned and B) Does anyone have a shortcut?
Thanks!!

Thanks for confirming my fears
Its a shame that since its such a long standing thing, it hasnt actually been added to the knowledgebase... which when we started this project (long before this schmozzle of a new system was introduced) was the most relevant place to look. When I start something, I tend to look in the KB.... not think "oh perhaps I should check the FAQ's in case there is a long standing issue that isnt contained in the KB".

Idocs neding in 64 status and not processed further

Hi
We have inbound idocs of FIDCC2 message type, which are set to be triggered immediately. However we have noticed that sometimes (not always) these idocs are in 64 status and are not processed further. We have to manually reprocess them.
What could be the problem? Where should we start investigating?
Any help would be appreciated.
Thanks
Mick

I think the comment by Gautham Vangaveti is probably correct.
We hit the same issue occassionally. We have IDOCS as trigger immediately, but at the time they try to process, there are no available work processes which can handle the IDOC and they sit at status 64.
There is an oss note 1333417 which describes the situation
https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1333417
And unhelpfully suggests changing over to processing by batch job, which is not always appropriate.
It may be worth enlisting help from you Basis team to try and indentify if those going to status 64 are occuring at the same time each day, and maybe looking to see what other processes are running at that time. If the load on the system can be managed then the problem may go away, it did for us.
Otherwise, Basis may be able to increase the number of work process which may also resolve the issue.

Idocs are not processed in the right order.

Hi,
I face a problem that when there are a large number of IDocs (Inbound) posted the Idocs are not processed in the right order.
Msg type: MBGMCR
any idea how this can happen?
what is the solution?
br
Karen

No answer

Report RBDAPP01 not processing IDocs in status 51

Hello guys,
I have a problem with the execution of some Inbound Idocs using program RBDAPP01.
Now the Idoc is executed in background with a job. Sometimes we have some locks because we receive idocs going to the same order, and then remain in status 51.
In the variant of the job we filled to execute Idocs with status 64 and 51, but the idocs that remain in status 51 are not processed, at the end we have to do it manually.
There is no parallel processo to avoid the locks.
Do you know how we can solve it?
Many thans in advance.
Regards,
Xavi.

i do have the same problem. is there an solution to this?

Idoc in 53 status but not processed completely.

Hi ,
Some of the ORDER Idocs are in 53 status, but the orders are not processed successfully and no PO created for these Idocs.
They got below warning message when I checked in WPER transaction code.
" Missing authorization: Purchase Order Create Purchasing Grou 110 " - "Workitems (tasks) were created for this IDoc"
This is happening once in a while for some of the idocs. Remaining all idocs are posting successfully.
Any idea what might be the reason?
Thanks
Deepthi.

Hello,
This seems to be an Authorisation issue, Kindly check for Purchasing Group 110, who are all assigned Buyers...
Then for those Buyers.. you can check what authorization is missing from Su53..
Compare with those who has authorisation to create PO Vs who does not have ..
you will have to provide the same authorisation to those users
Thanks and regards
PJ

Field BKPF-BVORG in idoc not processed

Similar Messages

Maybe you are looking for