IT0015 to IDOC Not running SAP Payroll

Hello everyone,
I am trying to get a newly configured wage type (a copy of M112 Commission) to be generated onto an IDOC via pc00_m10_otem. I have been unsuccessful so far.
Ultimately I want to create two wage types: A commission and a bonus which will be picked up during the normal payroll period.
Are there other steps besides creating a wage type? Please help!
Regards,
Mary

Hi,
please check the distribution model and ports you have created for LGART field. it is also impportant to check the logic of change pointers generation for LGART field.
i beleive there is a problem in the change pointers generation. pls check the logic from outbound side.
thanks
gayathri

Similar Messages

What are reasons to generate work schedules-not using SAP payroll or TM?

We have SAP ECC 6 HR and only pass a work schedule rule to our proprietory payroll system and have our own time and attendance system. The extent of our TM in SAP is just to have work schedules to attach to positions IT1011 and IT0007 on the employees. We are a very large 24/7 organization and have nearly 20,000 work schedules in use. It the past we have generated them out for 3 years and regenerate them as the come close to expiring.
My question is - what are some basic reasons for generating a work schedule? In our implementation I can't seem to find out why we need to continue doing it. We are able to attach an ungenerated work schedule to a position and a person.
Thanks in advance for any insight.

Generally the reasons why you would have a works schedule is for leave deduction, and possibly accruals, and also for automatic generation of overtime and shift penalties, public holidays. It could also further link into separate systems for payment purposes, or for attendance checks (i.e. EHS, rostering, training & event mgt, Sales & Distribution).
However, if your rostering/award interpretation is being handled in a separate system, and this information is being passed to a separate payroll system, then it would seem redundant to have work schedules in SAP.

Idocs not reaching SAP R3 from XI

Hi All,
I have a File to IDOC scenario, in which i need to process a text file of size 1 Mega Byte. The file from Leagacy reached XI and this has to create 12000 idocs in target R3 system. I can see the idocs(12000) in the IDOC Adapter but these idocs have not reached R3.
In SM58 I see an entry for this with the status "Transaction Executing". This entry is pending since 3 days. This always results in "Time exceeded out", and Iam manually executing it with F6 but still the status shows "Transaction executing".
There are no entries in SMQ1 & SMQ2
I want to push these idocs to R3.
Any suggestions on this will be helpful
Regards,
Santosh

Santosh,
Use IDOC packaging as shown in Michal's blog
/people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change
Also, try increasing time out values
/people/michal.krawczyk2/blog/2006/06/08/xi-timeouts-timeouts-timeouts
Regards,
Jai Shankar

IDOC Monitoring issue - job BPM_DATA_COLLECTION* not running.

Hi all,
We are facing an issue with BPM "IDOC Monitoring" (under application monitoring), which we have setup to monitor Inbound and Outbound Idocs in 2 separate R/3 systems.
In one system it works fine, and measured values are returned each time the monitor is set to run according to the specified schedule.
However, for another R/3 system, the monitor has never run, even though the settings are identical in the monitoring setup.
From reading the Interfaces Monitoring Setup guide, I found that this monitor depends on a job called BPM_DATA_COLLECTION* which runs in the monitored system. In the system where monitoring is functioning correctly, I can see this job is completing successfully at the time the monitor is set to run. All I find is completed jobs - no scheduled or released jobs present.
However, for the system where the monitoring is not functioning, I found that this job is not running, but that the job is sitting in scheduled status instead.
When I tested manually running the job in this system, it ran successfully, and in Solution Manager the monitor brought back the measured value, so the monitor only ran successfully when I manually ran the job in the monitored system.
I read notes 1321015 & 1339657 relating to IDOC monitoring. 1321015 appears to be more relevant, yet it does not exactly describe my issue - it mentions the job BPM_DATA_COLLECTION* failing rather than just remaining in scheduled status which is what I see.
Anyone else see this issue before?
On a more general point - the standard BPM Setup guide doesn't really go into much detail on IDOC Monitoring, and makes no mention of what is happening in the background, i.e. the job BPM_DATA_COLLECTION* being created and run as per schedule. This info is found in a separate document "Interface Monitoring Setup Guide".
Is there any single document which describes fully what happens both in the Solution Manager and the Monitored systems when BPM is activated? For example, to describe which monitors require jobs to be run, which monitors require additional setup in monitored system, etc? A document such as this which describes exactly the process flow for each monitor would be very useful in troubleshooting issues going forward.
Thanks,
John

Hello John,
most probably the user assigned to the corresponding RFC READ connection that connects SolMan with the backend system doesn't have proper authorization to release a job. That's why it is only created/scheduled but not released. Verify if the RFC user on the backend has the latest CSMREG profile assigned according to SAP note 455356.
You can also check if the latest ST-PI support package is installed on your backend system as the ST-PI usualy contain the latest definition of CSMREG.
Best Regards
Volker

Idoc not posted in sap system

Hi All,
i have configured the file to idoc and idoc to idoc scenario.
in sxmb_moni,the inbound idoc is fetching one port and the out bound idoc is fetching the default port,how can i config the port that is idoc comming from sap system.
in interface mapping i am not able to assign the operational mapping that is created in IR, it is fetch the default name space of the idoc ,which is not to our operational mapping created in IR.
Regards,
reddy

in sxmb_moni,the inbound idoc is fetching one port and the out bound idoc is fetching the default port,how can i config the
port that is idoc comming from sap system.
In Message Mapping enable the EDI_DC40 segment and then give value to the SNDPOR/ RCVPOR ....once done in receiver IDOC channel check the Apply Control Record from Payload....Michal has written a blog on EDI_DC40 segment check it once.
in interface mapping i am not able to assign the operational mapping that is created in IR, it is fetch the default name space
of the idoc ,which is not to our operational mapping created in IR.
This behavior is correct....IDOC will refer to its own namespace and not to the one created in IR.....and this should not cause any issue while assigning mapping in Interface Determination....if it is causing an error then you have not selected the objects properly.
Regards,
Abhishek.

SBO_Backup Service is not Running In SAP Business one 8.8

Hi Experts,
Here We have Recently Upgraded from SAP Business one 2007 to SAP Business one 8.8.
Previously the SBO_Backup service In Server Tools was running proberly,
But after Upgrade the Backup service is not running .
Kindly Give us your value solutions..
Regards,
M.Senthilnathan

Hi,
I Am Using Windows Server 2003 Small business Server edition.
I have checked Ur solutions.
Am running Server tools in Administrator Login only with Full Permissions.
The License manager and DI server is running Only The SBO_Backup service is not Running!!!
Regards,
M.Senthilnathan

MATMAS01 IDOC not reaching to SAP XI via report program.

Dear Experts,
WE are facing small challenge.
I searched on SDN on scenarios: IDOC not reaching to SAP XI. But could not find exact solution t oour scenario.
Problem:
MATMAS01 IDOC is not reaching to SAP XI via report program and is in status of 03 on SAP system. And there are not entries under SM58.
Under SAP XI system IDOC entry is not reflecting under IDX5 transaction, I tried to delete meta data of MATMAS01 thru IDX1 and uploaded again but still IDOC is not reaching to SAP XI.
The strange is that MATMS01 IDOC is reaching to XI via WE19 test tool. So PORT and RFC destination settings betweeen R3 and XI is also correct.
What could be the wrong ?
Thanks
Divyesh

When sending Idoc from R/3,
Settings at R/3
create one port at WE21,
Create Partner Profile for Outbound Message type in WE20.
settings at XI
Create one port in IDX1
Import Matadata in IDX2.
Create complete scenario in ESR for Idoc sender, also import IDoc in Imported Objects.
Check these settings & send test idoc using WE19.

SAP Query not running

Hi,
I am doing SAP query, If I select Company Code, i need to get the resule of
GL a/c, Buss Area, Cost Center, Profit Center
For this in table joints i taken KNA1, KNB1, SKB1, CSKS
then also i could not run the report.
Rgds
sunfico

Hello
When you have chosen a query and a user group on the initial screen, you can execute the query online or in the background.
Executing Queries Online
Executing Queries in the Background
Improving Response Times
Interactive Functions for ABAP Lists
Direct Interaction
Check this link for further notes executing queries
http://help.sap.com/saphelp_erp2005vp/helpdata/en/b7/26ddebb1f311d295f40000e82de14a/frameset.htm
regards

IDOC not reaching XI from SAP

Hi,
I am trying to fire IDOC (DEBMAS) from SAP to XI. The basic Idoc has been exxtended to add some new segments. The required configuration has been done on SAP and XI side(partner profile on SAP and IDX1/IDX2 on XI).
However whenever I fire this idoc from SAP, it shows that Idoc has been triggered but am not able to see the same in SXMB_MONI in XI.
Please let me know if you have any clues

Hi Anand,
The monitoring in SXMB_MONI can only inform u about integration engine.
SM58 errors occur if a RFC destination does not work.
Also what is the Status Text message you see in the SM58 ?
Anyways have a look at this Blog....
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
Regards,
Abhy
Message was edited by: Abhy Thomas

IDOC is not reaching SAP from XI

Hi all,
The IDOC that I'm sending from XI is not reaching SAP.
I have tried all most all possibilies. In SXMB_MONI I'm able to see the IDOC gets created successfully (with no error).
I have re-checked the partner profile, SMQ1, Config etc.
Please help me to debug.
Thanks,
AJ.

AJ,
Check if you have a chequered flag on both sides of your message ibn SXMB_MONI?
Check the log of your TRFC in transaction SM58
gards,
Bhavesh
Message was edited by: Bhavesh Kantilal

Payroll - Check for Previous Period which did not run before

Hi all,
I have an employee who was terminated hence payroll was not run for him from his poiint of termination, i.e. he was terminated from period 03, 04, 05 onwards.
Now currently it is period 06,... I wish to run payroll for him, for his period 03, 04, 05, I need to be able to detect that I am running payroll for the 2 conditions:
1) That the period i'm running FOR (03,04,05) is before the currnet period.
2) And that for periods 03, 04, 05 I am running the payroll for this employee for the FIRST TIME.
Are there any commands in the schema that I can use to know this?
Regards,
Kevin

Hi Kevin
When simulation or payroll is running for the employee at the bottom of the screen it tells you which period it is processing as payroll runs thru each pay period.
The log when expanded also does the same. If an employee has not had pay run for 3 months prior it is still a retro. Also check info type 0003 see if the PDC recalc date has been set and this will tell you how far back pay will run, if pay has been run the pay results.
if its the schema commands then print your paryoll schema to the screen and then expand and search for "retro", this will give you the retro commands or run program RPDASC00 and fill in the schema name etc.
Rona

SAP j2ee engine is not running error while applying patches.

Hi all,
Iam in the process of aplpying patches using JSPM tool , for some of them iam getting the error messages , when i checked the log file for this tool it says:
SAP J2ee engine is not running , unable to login to <HOST name> with id <Login id>.
Iam very new to this activity ,can anybody help me in this regard , i wil be very thankful.
Thanks and Regards.
Niyati.

Hi,
What exactly do you see when you say that the status in the MMC is OK? I don't think it can be green if you say that you get a message saying "Service Unavailable" when you try to login. If you get that message, it means that the service hasn't either been started or could not be started in case of an error. In this case the server status in the MMC should be yellow (or gray in case none of the services could be started)...
Could you perhaps check it again? Another point to check would be if the connection to the database is OK. If you are using MySQL MaxDB, you could use the Database Manager tool to check this. Sometimes the log files fill up the database and the server cannot start because the database is full. In such cases you will need to clear the logs and then restart the entire cluster.
Sameer

IDOC not Received at XI

Hello folks ,
I need to send a idoc from r/3 to xi. i have made all the necessary configuration in r/3. iThis s a production sytem ....have checked on R/3the IDOC is succesful at we02
checked BD87- IDoc sent to SAP system or external program
SM58 no errors...
wen i checked at XI with the particular IDOC number iI dont find an entry what could be the reason .How to resolve the same.
Regards,
Robin

Thanks guys .. thanks for ur quick response
Solution : Had to run this job RBDMOIND ...(particular IDOC NO, was not sent to XI )
Edited by: Robin on Jul 30, 2010 3:22 PM
Edited by: Robin on Jul 30, 2010 4:43 PM

An out-of-sequence check is not permitted for payroll type B

We had to do advance payments for 4 pay periods for an employee through offcycle workbench. One of the checks was wrong so we had to reverse it. It is an out of sequence reversal. Now when i try to do a correction run , it gives me an error An out-of-sequence check is not permitted for payroll type B
How can i run the correction run now. Please help
Edited by: sagarika sharma on Aug 14, 2010 6:29 AM

Check with SAP note 1425764,696067 and 1127119.
Mohan

Error while running SAP HR activ sync

Hi Geeks,
Got this issue while I run my SAP Active sync.
"Caused by: com.sap.mw.idoc.IDoc$Exception: (8) IDOC_ERROR_INITIALIZATION: Could not initialize SAP Java Connector IDoc Class Library. Found SAP Java Connector version 2.1.6 but version 2.1.8 or a higher patch level is required."
I have SAPJco 2.1.6 in my class path and the Sap Idoc is of 2.1.8 but I am not able to find the earlier version of sap idoc jars in serverice.sap.com.
Let me know ur thoughts on the same.
Regards
Jeyanth

Hi Choon,
First of all do you have the installation guide on you, if not please get one from the marketplace. The one I have suggests the following at the end of installation -
Since we are installing IDES, I am told just click retry once more (you will get the error again), and
then click OK to end the installation. This is valid for SAP R/3 4.7 ext.1.
See if this removes the error you are getting, please awards points if you succeed, and let me know.
Thanks,
kind regards,
M. Nizam

IT0015 to IDOC Not running SAP Payroll

Similar Messages

Maybe you are looking for