Batch level acknowledgments from Bank not getting processed.

We are using BCM, (Bank Communication Management) module. We send pain.001.001.03 xml files to bank for the payment and receive three levels of acknowledgments or Pain.002.001.03 files: File level (based on MsgId) , batch level (basedon PmtInfId) , transaction level (based on EndtoEndId)
however, in the standard mapping of CPON (Collective Payment Order Notification) PmtInfId (OrgnlPmtInfId in pain.002.001.03) is mapped in
the same place as MsgId (OrgnlPmtMsgId in pain.002.001.03)[This is as per the mapping given in note 1803299]
So, when PmtInfId is different than MsgId (and that happens whenever there are more than one batches in a payment due to more than one payment methods or currencies) then we get an error in
system that :
'No batch found for the incoming header id ...'
We've already applied note 1498987, but that makes no difference.
So please tell us how to process the batch level acknowledgments where OrgnlPmtInfId is different than OrgnlMsgId in the inbound pain.002.001.03
files.

Similar Messages

Automatic update of number ranges in FBN1 is not getting processed

Automatic update of number ranges in FBN1 (current status) level is not getting processed.
Tried posting a customer payment document in the system though number ranges are maintained for the year 2015 the number ranges are not overlapped last year all documents are closed but still the numbers are not been picked automatically in FBN1 kindly help in this issue

Hello Rajesh
Please verify if number ranges are maintained correctly, verify same using transaction OBA7. Also ensure that external assignment is unchecked in FBN1. Share screenshots if possible.
Regards
Aniket

Savings Plan Contribution is not getting processed in Payroll

Hello Friends,
We are in the process of upgrading our system from 4.0 to 4.7, After correcting the schema as per the release/OSS notes, we are getting Savings Plan Contribution as blank (Retirement Savings).
Cumulation values are coming thru right but current period contribution is missing.
Earlier we had P0169 with P61, now we do not see processing class(PCLS)61 in the PCLS list. Our earlier wage types were referring to PCLS 61, I am not sure if this is causing an issue.
Please let me know if you have any faced similar situation and have an answer.
Thanks & Best Regards
ravi

Ravi,
Appriciate if you could share the solution for your problem in savings plan contribution is not getting processed in the payroll. As I am facing the same kind od problem for my new configured benefit plan ROTH 401k plan.
Please let me know the solution.
Thanks & Regards,
Sunita

Bulky Message are not getting processed

Hi All,
Recently we have upgraded our XI systems to EHP4.
After upgrade Bulky files are not getting processed into XI system. Small files are getting processed successfully.
Earlier we had faced same issue at that time we have maintained some parameters in transaction RZ10, RZ11, SXMB_ADM-->
Integration Configuration--> HTTP time out parameter.
Same parameters are still there. But now the message is not getting processed in XI when we check into sxi_monitor. Message mapping is also not seems to be a problem as we havnt put any bulky logic over there.
The message is not getting processed ahead of Receiver Grouping . Please find attached log from Performanceheader
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SAP:RunTimeItem>
<SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
<SAP:Timestamp type="begin" host="evoxicqab">20091210134229.930472</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
<SAP:Timestamp type="end" host="evoxicqab">20091210134232.052577</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="begin" host="evoxicqab">20091210134232.059576</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="end" host="evoxicqab">20091210134232.07151</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
<SAP:Timestamp type="begin" host="evoxicqab">20091210134232.071518</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
<SAP:Timestamp type="end" host="evoxicqab">20091210134237.239947</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
<SAP:Timestamp type="begin" host="evoxicqab">20091210134237.241179</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
<SAP:Timestamp type="end" host="evoxicqab">20091210134237.250385</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
<SAP:Timestamp type="begin" host="evoxicqab">20091210134239.999045</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
<SAP:Timestamp type="end" host="evoxicqab">20091210134240.001292</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
<SAP:Timestamp type="begin" host="evoxicqab">20091210134240.001413</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
<SAP:Timestamp type="end" host="evoxicqab">20091210134240.026156</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name>
<SAP:Timestamp type="begin" host="evoxicqab">20091210134240.026164</SAP:Timestamp>
</SAP:RunTimeItem>
</SAP:PerformanceHeader>

Hi
Have you checked this thread, same discussion here
Performance of XI Interfaces
Also check this blog
/people/michal.krawczyk2/blog/2006/06/08/xi-timeouts-timeouts-timeouts
Regards
Ramesh

IDOCS Error - Not getting processed automatically

Hi All,
We are loading hierarchy for a Product from R/3 system using the standard datasource.
When we execute the info package, IDOCs are not getting processed automatically.
We are facing the below error message.
Error when updating Idocs in Business Information Warehouse
Diagnosis
Errors have been reported in Business Information Warehouse during IDoc update:
No status record was passed to ALE by the applicat
System Response
Some IDocs have error status.
Procedure
Check the IDocs in Business Information Warehouse . You do this using the extraction monitor.
Error handling:
How you resolve the errors depends on the error message you get.
But when we goto BD87 and process the IDOCs manually, these are getting posted and the hierarchy is loading.
Can someone please guide me on what is the issue with the IDOCs and how to make them to post automatically.
Thanks in Advance
Regards,
Sachin

Hi,
This will happen due to Non-updated IDOCu2019s in the Source system i.e., occurs whenever LUWu2019s are not transferred from the source system to the destination system. If you look at RSMO of the status tab, the error message would appear like u201CtRFC Error in Source Systemu201D or u201CtRFC Error in Data Warehouseu201D or simply u201CtRFC Erroru201D depending on the system from where data is being extracted. Sometimes IDOC are also stuck on R/3 side as there were no processors available to process them. The solution for this Execute LUWu2019s manually. Go to the menu Environment -> Transact. RFC -> In the Source System from RSMO which will asks to login into the source system. The u201CStatus Textu201D for stucked LUWu2019s may be Transaction Recorded or Transaction waiting. Once you encounter this type of status Execute LUWu2019s manually using u201CF6u201D or Editexecute LUWu2019s(F6).Just keep on refreshing until you get the status u201CTransaction is executingu201D in the Production system. We can even see the stuck IDOCu2019c in Transaction BD87 also.Now the data will be pulled into the BW.
Hope it helps a lot.
Thanks and Regards,
Kamesham

Data packet not getting processed

Hi SDN's
I m loading data from one ODS to 4 regions , the source ODS is successfully loaded from der to the data targets the load is getting failed or taking loang time .
upto transfer rules the data is successful, in update rules data packets are not getting processed
kindly suggest solution, points will be assigned
thx in advance

Hi Katam,
In the target ODSs go to the monitor screen for a particular request -> in the menu bar go to environment -> transactRFC-> in the datawarehouse -> give the ID and date -> execute.
Check if there are entries in that. Usually this queue will be stuck and you need to execute the LUWs in the queue manually.
if it says transaction recorded u need to execute it manually
Please revert if any issues
Edited by: Pramod Manjunath on Dec 19, 2007 4:48 PM

Article IDoc not getting processed in PI for particle article type

Hello All,
I have an strange behaviour in my system.
i.e 1, we are creating an article IDOC by using BD10 for particulat article type.
2, IDOC created succesfully , then
3, Process the IDOC in BD87 to push the IDOC to PI system .
4, But i could not see the message in PI that too only for one article type.
I'm wondering why this is not getting processed only for one article type and not for others.
we also checked the basic filter for the message type in dist model and even i could not see any condition in PI also,
Is there any thing else i should check? can you please help us on this.
Regards , Sethu.

Hi,
Try to reimport the metadata of IDOC into PI in idx2. Also check the port definition in ECC and whether the segment is released or not. Please go through the below discussions it may help you.
EDISDEF: Port XXX segment defn E2EDK35 in IDoc type ORDERS05 CIM type
IDoc 0000000000181226 was saved but cannot or should not be sent
Regards,
Priyanka

Entry not getting processed

I have an Non recurrening Multiple Entries allowed element to an assignment which is not getting processed when i run payroll.
Please help
Thanks

This is to ensure that results generated by the future payroll runs are correct. Lets take a simple eg.
You have a pension element which would be 10% of Gross Pay_YTD.
Run Payroll for Jan (Gross Pay) = 1000 -> Pension = 100 (10% of 1000).
Run Payroll for Mar (Gross Pay) = 1000 -> Pension = 200 (10% of 2000).
Run Payroll for Feb (Gross Pay) = 1000 -> Pension = 200 (10% of 2000 as _YTD of Feb does not account March figures).
In the above case the Payroll Run results generated by March would be incorrect.
So once you run Payroll for March, you can not run payroll for Feb. If you require any additional payments to be made in Feb (after Payroll for Feb and March are processed), you can run Retropay to bring forward the entries to next Open pay period.

IDOC status 64 not getting processed.

Hi Gurus,
      I have a problem where IDOC's with status 64 are not getting processed via background job. the IDOCs weere getting processed with the background job till today evening, but suddenly no changes were made and the processing of IDOC's with status 64 has stopped and they keep filling up, when i checked the log of the Background job it says finished, and the log has the following information,
17.09.2009 19:05:23 Job started                                                                   00           516          S
17.09.2009 19:05:23 Step 001 started (program RBDAPP01, variant POS_IDOCS, user ID SAPAUDIT)      00           550          S
17.09.2009 19:05:25 No data could be selected.                                                    B1           083          I
17.09.2009 19:05:25 Job finished                                                                  00           517          S
Kindly advise on this.
Regards,
Riaz.

When i process the IDOC's using BD87, they gets processed wiwth out aany issues no dump is displayed, idoc gets a status 53 after processing via BD87.
There is another problem how ever there are other jobs scheduled to run in the background other than this background job which are getting cancelled and have two different error logs for different jobs they are as follows.
1) 18.09.2009 02:00:06 Job started                                             00           516          S
18.09.2009 02:00:06 Logon not possible (error in license check)             00           179          E
18.09.2009 02:00:06 Job cancelled after system exception ERROR_MESSAGE      00           564          A
2) 18.09.2009 00:55:27 Job started                                                          00           516          S
18.09.2009 00:55:27 Step 001 started (program RSCOLL00, variant , user ID JGERARDO)      00           550          S
18.09.2009 00:55:29 Clean_Plan:Gestartet von RSDBPREV                                   DB6PM         000          S
18.09.2009 00:55:29 Clean_Plan:beendet                                                  DB6PM         000          S
18.09.2009 01:00:52 ABAP/4 processor: DBIF_RSQL_SQL_ERROR                                00           671          A
18.09.2009 01:00:52 Job cancelled                                                        00           518          A
This is a production server and the Licence is valid till 31.12.9999, and has no issues with the license.

RSEOUT00 - Idoc not getting processed

Hi All,
I have few idocs in prod.system with status 30 and they are not getting processed using RSEOUT00.
I tried using back ground job / forgrond / BD87 also but they are not getting converted to 03 status.
receiver port is xmlgen.
Any thing like idoc lock ? or something other that is preventing it process ?
Please let me know if anything.

check out the multiple threads in SDN regarding this issue
idoc remains random in status 30
some of the common pointers looks to be locked IDOC (check in SM12), SM58 to see if anything is in the RFC queue (though I doubt that would be the case)..
How are you generating your idoc? standard FM or MASTER_IDOC_DISTRIBUTE?

Batch Input Session for RFUMSV50 is not getting processed.

Dear All,
When i am trying to transfer the Service Tax Inetrim account to Service tax final account with the help of the program RFUMSV50 the batch input session is getting generated without any error. But when i process the same in SM35 it is not getitng processed.
Please advice on this.
Regards,
Rajeswari Shankar.

Hello Rajeswari,
Yes, this is normal.
When batch input sessions is generated with any error, this does not mean that you can execute it after via SM35 without any error
Moreover, you have the option in SM35 to execute it and with option "display error only", so this means that it can happen that there is no error
For example, the profit center is mandatory, and it is missing in the document. In that case the system will display error and ask you to fulfill the profit center
Please tell me, which error you have (message number)
Thanks
Tarek

Why am getting this ME083 error in BATCH JOB, where as ONLINE not getting?

Hi Experts,
Am creating Purchse Requisation by using BAPI ---> BAPI_PR_CREATE.
If I run ONLINE, Purchse Requisations are creating in EBAN table, with out any erorr messages, fine.
If the same prog. is scheduled as BATCH JOB in production, the Purchse Requisations are creating, fine, but, there is a ERROR MESSAGE in JOB LOG, saying that " ENTER PLANT " of M essage ID& # is "ME 083 "
So, let me know that,
1 - Why am not getting this error message, If I run it ONLINE?
2 - Even though there r error message in JOB LOG (as I mentione din the above), Why the Purc. requisations are creating?
3 - How to track that, from Where this error is coming in BATCH JOB, How to debug the BATCH JOB, after its scheduling?
4 - How to fix it?

It is not uncommon for informational/warning messages to appear when a BAPI is run in batch.
Such messages do not prevent the completion of a job, but may provide information about the status of processing.
When you run the job online the message may just flash briefly on the bottom of the screen, and you might not even notice it.
I get similar messages when I run other BAPIs, where the message is logged but the process continues to run.
To address the question of the message itself, if you look at the code underlying the BAPI, for example, include L2105I01, which contains the methods, you can see the place where the message is issued.
The message is issued if field PR_TYPE in the header structure is initial.
This is fairly easy to find just by examining the source behind the BAPI and the methods that it uses.
You can navigate to include L2105I01 just by clicking on Method process in BAPI_PR_CREATE, just as you can with any other navigable object in ABAP.
You should see this in BAPI_PR_CREATE around line 108.
CALL METHOD l_ref_bapi->process( ).
Double click on process.
Method renumbering is then called by Method process if the actyp = hin (a constant meaning add/create which is set in BAPI_PR_CREATE), and if ITEM_INTVL (Item number interval) is not initial.
Double click on Method renumbering.
Method renumbering then checks if field PR_TYPE is initial, and if it is, then the message 083 that you are getting will be issued. You will also see that the message is issued as a warning only, which is why the document is still created.
You can drill down through the code by double clicking, as usual with navigation.
I found this initially by clicking method set_header, which brought up the include with the method code. I then searched for 083, which is the message id. I then backtracked to find out what the path to Method renumbering was.
Always do a little digging in the source, the message has to come from somewhere. If the first search does not get a hit, try the next one until you exhaust the possibilities. I chose set_header, since it appeared to be specific to the function of the BAPI, and something like that will usually be the best place to start. In this case, it took me right to it.
Brian

About the effect for batch level conversion from material to plant level

Dears,
Now we use batch management at material level in our system, now we want to change to batch level from material level to plant level, what effects or risks it will bring during the process of conversion?
Thanks a lot
Zhongkai

Hi
check the following SAP help link it is very helpful:
http://help.sap.com/saphelp_40b/helpdata/es/d2/1d4b6e5733d1118b3f0060b03ca329/content.htm
at the link you can find the following
Specify batch level and activate status management
In this IMG activity, you specify the following:
the level at which batch numbers are unique
whether batch status management is active in the client
the plants in which batch status management is active
the initial status of new batches
Batch level
Batch numbers can be unique at the following levels:
at plant level
at material level
at client level for a material
If you choose plant level, the batch number is unique in conjunction with the respective material and the plant. If you choose material level, the batch number is unique together with the material. At client level, the batch number is unique in the whole client.
To change the batch level, you have to start a conversion program. This program first checks whether conversion is possible and outputs an error log containing all batch numbers that occur more than once at the new level. Now you need to manually transfer these batch records to numbers within Inventory Management using a transfer posting 'material to material'.
If you change the level from plant level to a higher level, it is possible that batches with the same batch numbers in different plants are actually identical. In this case, all you have to do is remove stocks (including previous period stocks) so that all batches with the same batch numbers, except one, can be reorganized.
When you convert from plant level to material level, the material is then to be handled in batches in all plants in which it is defined.
Standard settings
In the standard R/3 System, batches are unique at plant level.
Activities
To change the batch level, proceed as follows:
      1. Choose the level at which you want your batches to be unique.
      2. Save the new settings and choose Back.
      3. Select function Batch level -> Conversion.
      4. If necessary, carry out the conversion in test mode first.
Further notes
Note that you cannot reset conversion from plant level to a higher level in the standard.
If you create a client by copying an existing client, initially, there are no settings in the target client at batch level. The system makes the settings in the target client only when you have carried out an activity (maintaining master data or posting a goods movement, for example).
SETTINGS BEFORE/AFTER CLIENT COPY:
Source client Target client
Client level Material level
Material level Material level
Plant level Plant level
Batch status management
Batch status management is an additional function provided by the standard R/3 System.
Standard settings
Batch status management is not active in the standard R/3 system.
Activities
To activate batch status management, proceed as follows:
      1. Choose Batch status management active.
      2. Save the new setting and choose Back.
      3. Choose Batch status management -> conversion.
      4. If necessary, carry out the conversion in test mode first.
Further notes
Batch status management is linked to the batch level. At material and at plant level, the status management settings are valid within the client, that is for all plants. However, if you have defined batches to be unique at plant level, you have to select the plants in which status management is to be active using function Plants with status management.
If you activate status management, all existing batches are assigned status 'unrestricted'. If you deactivate status management, the systems transfers all restricted batches to unrestricted stock within conversion. Restricted stock only exists if status management is active.
If you create a client by copying an existing client, status management is automatically activated if batches exist in the target client, independent of the settings in the source client. If no batches exist in the target client, it is not activated. In this case, you have to activate or deactivate status management manually, if required.
Plants with batch status management
Activities
To select the plants in which status management is to be active, proceed as follows:
      1. Set characteristic Batch status management for those plants in which batch status management is to be active.
      2. Save your settings and choose function Back.
      3. Choose function Batch status management -> conversion
      4. If necessary, carry out the conversion in test mode first.
Initial status of a new batch
Using this function, you can specify for each material type which initial status new batches are to be assigned. However, if you use a quality management system, this specifies the status of the batches.
Hope it will help
Best Regards

Message ID missing and file not getting processed.

Hi Experts,
This is regarding an issue in Production system.
Scenario: File to File.
SAP PI verison : 7.0
Interface data coming from B1 system to PI is having an issue.
PI sender channel picks up the file from B1-FTP server,the file gets archived too, however the message ID is not getting created in communication channel monitoring and message is lost. It is not traceable.
The message is not processed further, not visible in receiver channel nor in sxi_monitor.
we have tried cache refresh, adapter metadata refresh, also tried creating new channels however, issue persists intermittently.
Any help/suggestion would be highly appreciated.
thanks and regards,
Praveen T

Hi Praveen
Is it possible for you to provide the screenshot of logs from your sender
communication channel when the file is picked up from the FTP Server?
Also advise if the FCC is used in the sender channel, if yes check in case
it is failing.
Regards
VJ

SM35 session is not getting processed in background

HI Folks,
I am using BDC (open group, Insert group, Close Group) to create a SM35 session and calling RSBDCSUB program to process created session.
this program is being executed in background job,
Issue is, when this program is scheduled to run with my user ID(dialog user) is running fine i.e. session is getting processed completely.
however, when job is schedule with background user, session is getting created with status NEW, but not processed, we have to go to SM35 and manually process that session.
Does anybody come across such issue, What could be the reason, I could see authorization might be the problem.
please advice.
Thanks,
Brahma,

Hi brahmanandam,
You need use RSBDCSUB and submit it using the session name u generated...
SUBMIT RSBDCSUB AND RETURN
USER SY-UNAME
using selection-set 'VAR'.
Where VAR is ur variant name

Batch level acknowledgments from Bank not getting processed.

Similar Messages

Maybe you are looking for