Community
Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Read only

Loading Onshore Time Writing in T-Code CAT2

Former Member

‎2011 Sep 20 8:57 AM

0 Likes
757

Experts,

Does anyone have any idea in regards to loading Onshore Time Writing using T-Code CAT2 in Data Conversion?

I am currently exploring this and was thinking of using a Recording in LSMW- but due to the volume of data- estimated around 10,000, I wanted to find out if anyone has another method such as an IDoc or BAPI etc.

Thanks,

Muna

Experts,

Does anyone have any idea in regards to loading Onshore Time Writing using T-Code CAT2 in Data Conversion?

I am currently exploring this and was thinking of using a Recording in LSMW- but due to the volume of data- estimated around 10,000, I wanted to find out if anyone has another method such as an IDoc or BAPI etc.

Thanks,

Muna

Reply
3 REPLIES 3
Read only

RaymondGiuseppi
Active Contributor

‎2011 Sep 20 9:13 AM

0 Likes
655

Look at the following BAPI

- [BAPI_CATIMESHEETMGR_INSERT|http://www.sdn.sap.com/irj/scn/advancedsearch?query=bapi_catimesheetmgr_insert]

- BAPI_CATIMESHEETMGR_CHANGE

- BAPI_CATIMESHEETMGR_DELETE

Regards,

Raymond

Read only

Former Member
In response to RaymondGiuseppi

‎2011 Sep 20 9:31 AM

0 Likes
655

Thanks Raymond.

I am looking into using the BAPI, but as I only have a requirement for 10 fields- have you ever used a Recodring to load this as we only have historical data so we will only be loading the hours for one day to make up for the previous weeks.

Read only

RaymondGiuseppi
Active Contributor
In response to RaymondGiuseppi

‎2011 Sep 20 9:56 AM

0 Likes
655

The BAPI will complete the input data as transaction CAT2 does, so, depending on your Customizing, you may only require few fields (pernr, duration, cost center...)

If it is a "one shot" upload from Legacy system, before going live, you could also "reduce" the checks in Customizing, upload and validate data, then re-transport final Customizing.

Regards,

Raymond