BAPI_QTASRVAPS_SAVEMULTI2 Date Format

[joerg_arndt]

Hi Friends

I need help with the following problem.

The BAPI u201EBAPI_QTASRVAPS_SAVEMULTI2u201C structure u201EBAPI10009QTAHEAD2u201C expects a Date u201EVAL_FROM und VAL_TOu201C but I have no idea how it has to looks like.

In the Table it looks like 19.891.231.230.000. There is a FM u201E/SAPAPO/TR_DATETIME_CONVERSION u201E

but nothing will fit.

Any help is appreciated.

Thanks in advance

Jimbob

[Former Member]

Hi Jimbob,

I am not able to find BAPI like BAPI_QTASRVAPS_SAVEMULTI2. Is there any typing mistake..!

Thnx

Chetan

[Former Member]

Hi ,

u can use FM

CALL FUNCTION 'CONVERT_INTO_TIMESTAMP'

EXPORTING

I_DATLO = LT_FILE-ZETA_DATE

I_TIMLO = SY-UZEIT

IMPORTING

E_TIMESTAMP = DELDATE.

Hi Joshi ,

its for APO systems.

Regards

Prabhu

[Former Member]

Isn't it available in R/3 repository/....????

Thanks

Chetan

[joerg_arndt]

Thank you Prabhu,

not bad but not good enough.

The expected field length in LSMW is 16 but the generated timestamp will be 18.

And by the way, I have the datetime in this 19.891.231.230.000 format.

With /SAPAPO/TR_DATETIME_CONVERSION I can convert it but still not the right format.

Any other suggestion.

There is no Doku for the BAPI, or?

I'm realy curious.

Rg. Jimbob

[Former Member]

>

> Thank you Prabhu,
> not bad but not good enough. 
> The expected field length in LSMW is 16 but the generated timestamp will be 18.
---> this is only for display , internally it will take 14chars only + one space .
char 8  for date ,6 chars for time and 1 space u will get , try to check in the debug mode , then u will come to know. And by the way, I have the datetime in this 19.891.231.230.000 format.
> With /SAPAPO/TR_DATETIME_CONVERSION I can convert it but still not the right format.
> Any other suggestion.
> There is no Doku for the BAPI, or?
> I'm realy curious.
> Rg. Jimbob

regards

Prabhu

[joerg_arndt]

Thanks Prabhu, thats great.

[Former Member]

Hi Guys,

I know it is too late to reply for this post, but still i would like to do. You can pass the time stamp value as such(without the ".", Ex: 20080630235959) to the BAPI it will manipulate the data and load it into the system properly.

I came across a situation when we have multiple Quota for a single Material (due to different validity dates), the BAPI ( i am configuring and running it through LSMW-BAPI) overwrites the entries and in the end it ends up with creating only one entry. So i can able to see only one Quota for one Material as the others are overwritten. But if i run the BAPI directly through the BAPI T-Code, it creates the multiple entries properly in the SAP system.

The parameter "AutoDelete" in the BAPI is made 'Initial'.

Do anyone came across such situation? Is there anything wrong with the LSMW field mapping Or with the BAPI itself ?

[former_member221541]

Hi,

We are also creating quota for external procurement using LSMW IDOC method and tries passing valid from and valid to date as yyyymmddhhmmsss and yyyymmdd but for both cases we are getting error as "Validity is not for an exact date".

Also one more input neeeded - in header we are passing 20100101 and in item I am passing value 19900101, so wanted to know if there is any check that item valdity date should be less or greater than header date.

please provide your input.

Yogesh