I am implementing S/4 HANA 1709 Embedded TM .Issue with Service PO and SES

Arjun,

your question is not clear. Could you be more specific and detail, step by step, the issue that you have? You can generate the PO and Service entry sheet from TM... and I dont understood what is the problem that you are facing.

Please, re-write your question; or send printscreen to be more clear..

Thank you,

FM

Hi Arjun,

S4 1709 support the function FSD -> PO, SES. There should be some configuration steps missing.

Best Regards

Clark Huang

Hello Clark ,

Sorry for late reply . I have done the Config which you pointed out for mapping the Purchase order type before i raised the thread ,which will be created from Freight Settlement document.

config for Charge type mapping with Service master

Config for FSD type mapping with Purchase document type:

But now we are facing 2 Issues :

1. If I manually click on the "POST" button on the Freight Settlement document , then the Life cycle status of Freight settlement document is changing to "POSTING STARTED" but no Service Purchase order is triggered .Instead a pop up message is shown as below

So we opted for the batch job /SCMTMS/SFIR_BATCH_TRANSFER to post the FSD and we succeed in creating the Service PO but no Service entry sheet.

2. But If I Post Service entry sheet manually in ML81N for the Service Purchase order created from FSD ,its getting posted and Accounting document is also posted .

We are now only stuck in the automatic Service entry sheet creation step . Please help me on this area . Let me know if any config is done to post it automatically .

Issue is resolved long ago .. sorry for late reply

Hello,

Firstly check in your system if the SES can be created Manually or not.

Secondly when you are opening the Service PO in ME23n and going to Services TAB in PO you might be getting an message below " customizing Incorrectly Maintained " We need to correct this by following the OSS 1382685

There will be 2 attachment word documents in the OSS where how we need to correct the entries in the table T162V and the Table control View of ML81n are given.

This basically happens because of :

-table control has less entries than T162V
- table control has more entries than T162V.

Compare the two entries and remove or add entries as required .

Please reward points if issue resolved .Let me know if any issue

Thanks

Arjun

Hello,

Firstly check in your system if the SES can be created Manually or not.

Secondly when you are opening the Service PO in ME23n and going to Services TAB in PO you might be getting an message below " customizing Incorrectly Maintained " We need to correct this by following the OSS 1382685

There will be 2 attachment word documents in the OSS where how we need to correct the entries in the table T162V and the Table control View of ML81n are given.

This basically happens because of :

-table control has less entries than T162V
- table control has more entries than T162V.

Compare the two entries and remove or add entries as required .

Please reward points if issue resolved .Let me know if any issue

Thanks

Arjun

Hello Harmesh,

Why to trying to post the FSD from TM?

In business scenario FSD are never posted individually they are posted via batch job /SCMTMS/sfir_transfer_batch.

In 1709 there's some issue with posting fsd by clicking post button from fsd itself . Basically basis team need to run the buffer cleaning batch job in interval to post it .if you are trying to post by clicking the POST button in fsd .

But I would advise to use the batchjob as it's the normal business practice

Thanks,

Arjun

Hello Experts,

Please give your suggestions. We are also implementing s4hana 1709 TM

I am getting error as Purchase order creation failed when transferring FSD to s4hana.

when I go to application log I see below message.

No master record exists for supplier.

For Carrier I entered Purchasing organisation data. there is no place to enter company code data for carrier. How to resolve this issue. Please help me.

Hello Venkat,

Please assign bp role vendor FLVN00 to the carrier.

Thanks,

Arjun