Migrating Service Purchase Orders with S/4HANA Migration Cockpit

[alexey_danshin]

Purchase Order Service Item Category is not supported by Migration of Purchase Orders (Only Open) Migration Cockpit object. In order to migrate Service PO object should be enhanced. In this blog post you will learn how to adjust it.

BAPI_PO_CREATE1 is used for PO migration. OSS note 2114353 - BAPI_PO_CREATE1: Template for creating service PO provide you with the sample test records for various business cases. I will use PO with one service line + single account assignment as example.

 

1 Create new Migration Project. In LTMC t-code fill Name and Mass Transfer ID.



2 Run LTMOM t-code. Open your migration project and create new migration object from Template.

Menu Project – Create Migration Object – From Template

Select Purchase order (only open PO)



Change Object description to Service Purchase order (only open PO). Also switch Names view via menu Settings -> Technical Names On/Off.

3 Adjust source structures. Append new structures below to lower level S_EKPO Item Data.

a - S_ESKL Create Comm. Structure: Acct Assgt Distr. for Service Line fields

Key	Name	Data Type	Length	Decimal Places	Amount Field	Column Header	Group Text	Check Table
1	EBELN	CHAR	10		0	Purchasing Document Number		S_EKPO
1	EBELP	NUMC	5		0	Item Number of Purchasing Document		S_EKPO
1	PCKG_NO	NUMC	10		0	Package number
1	LINE_NO	NUMC	10		0	Line Number
0	SERNO_LINE	NUMC	2		0	Seq. Number of Acc. Assignment Specifica
0	PERCENTAGE	DEC	4	1	0	Percentage for Account Assignment Value
0	SERIAL_NO	NUMC	2		0	Sequential Number of Account Assignment

 

S_ESKL foreign keys relationship

Field Name	Type of Foreign Relat.	Check Table	Field of Check Table or Literal
EBELN	Field	S_EKPO	EBELN
EBELP	Field	S_EKPO	EBELP
PCKG_NO	Field	S_EKPO
LINE_NO	Field	S_EKPO
SERNO_LINE	Field	S_EKPO

 



 

b - S_ESLL Lines of Service Package fields

Key	Name	Data Type	Length	Decimal Places	Amount Field	Column Header	Group Text	Check Table
1	EBELN	CHAR	10		0	Purchasing Document Number		S_EKPO
1	EBELP	NUMC	5		0	Item Number of Purchasing Document		S_EKPO
1	PCKG_NO	NUMC	10		0	Package number
1	LINE_NO	NUMC	10		0	Internal line number
0	EXT_LINE	NUMC	10		0	Line Number
0	OUTL_LEVEL	INT1	3		0	Hierarchy level of group
0	OUTL_IND	CHAR	1		0	Indicator: Outline line
0	SUBPCKG_NO	NUMC	10		0	Subpackage number
0	QUANTITY	QUAN	13		0	Quantity with Sign
0	BASE_UOM	UNIT	3		0	Base Unit of Measure
0	GR_PRICE	DEC	23	2	0	Gross price
0	SHORT_TEXT	CHAR	40		0	Short Text
0	OVF_TOL	DEC	3		0	Overfulfillment Tolerance
0	OVF_UNLIM	CHAR	1		0	Unlimited Overfulfillment

 

S_ESLL  foreign keys relationship

Field Name	Type of Foreign Relat.	Check Table	Field of Check Table or Literal
EBELN	Field	S_EKPO	EBELN
EBELP	Field	S_EKPO	EBELP
PCKG_NO	Field	S_EKPO
LINE_NO	Field	S_EKPO

 

c – add custom field in S_EKPO Item Data fields

Key	Name	Data Type	Length	Decimal Places	Amount Field	Column Header	Group Text	Check Table
	PCKG_NO	NUMC	10		0	Package number

 



 

4 Set up structure mapping as follow

Target Structure           T16_POSERVICES Communication Structure: Create Service Line

Source Structure	Description	Access Type	Mapping Type	Source Cardinality	Target Cardinality	Data Path Type
S_EKKO	Header Data	Mapping only	1:1 Relation	1	1	Not Applicable
S_EKPO	Item Data	LOOP AT TABLE	1:1 Relation	1	1	Default Path
S_ESLL	Lines of Service Package	LOOP AT TABLE	1:1 Relation	1	1	Default Path

 

Target Structure           T17_POSRVACCESSVALUE Create Comm. Structure: Acct Assgt Distr. for Service Line

Source Structure	Description	Access Type	Mapping Type	Source Cardinality	Target Cardinality	Data Path Type
S_EKKO	Header Data	Mapping only	1:1 Relation	1	1	Not Applicable
S_EKPO	Item Data	LOOP AT TABLE	1:1 Relation	1	1	Default Path
S_ESKL	Create Comm. Structure: Acct Assgt Distr. for Service Line	LOOP AT TABLE	1:1 Relation	1	1	Default Path

 

5 Map fields according data in table

Import Parameter	Parameter Value	Rule	Target Field
Target Structure T16_POSERVICES
SENDERFIELD	S_ESLL-PCKG_NO	MOVE	PCKG_NO
SENDERFIELD	S_ESLL-LINE_NO	MOVE	LINE_NO
SENDERFIELD	S_ESLL-EXT_LINE	MOVE	EXT_LINE
SENDERFIELD	S_ESLL-OUTL_LEVEL	MOVE	OUTL_LEVEL
SENDERFIELD	S_ESLL-OUTL_IND	MOVE	OUTL_IND
SENDERFIELD	S_ESLL-SUBPCKG_NO	MOVE	SUBPCKG_NO
SENDERFIELD	S_ESLL-QUANTITY	MOVE	QUANTITY
IV_ISOCD_UNIT	S_ESLL-BASE_UOM	CVT_ISOCD_UNIT	UOM_ISO
SENDERFIELD	S_ESLL-OVF_TOL	MOVE	OVF_TOL
SENDERFIELD	S_ESLL-OVF_UNLIM	MOVE	OVF_UNLIM
SENDERFIELD	S_ESLL-GR_PRICE	MOVE	GR_PRICE
SENDERFIELD	S_ESLL-SHORT_TEXT	MOVE	SHORT_TEXT
Target Structure T17_POSRVACCESSVALUE
SENDERFIELD	S_ESKL-PCKG_NO	MOVE	PCKG_NO
SENDERFIELD	S_ESKL-LINE_NO	MOVE	LINE_NO
SENDERFIELD	S_ESKL-SERNO_LINE	MOVE	SERNO_LINE
SENDERFIELD	S_ESKL-PERCENTAGE	MOVE	PERCENTAGE
SENDERFIELD	S_ESKL-SERIAL_NO	MOVE	SERIAL_NO
Target Structure T02_POITEM
SENDERFIELD	S_EKPO-PCKG_NO	MOVE	PCKG_NO
Target Structure T03_POITEMX
IV_VALUE	S_EKPO-PCKG_NO	SET_X_IF_NOT_INIT	PCKG_NO

Save and generate run time object.

 

6 Run LTMC t-code, open your project choose adjusted migration object and download Template.  Populate purchase order data as follow. Empty fields are omitted here.

 

Header data

EBELN	BUKRS	BSART	LIFNR	EKORG	EKGRP	WAERS
Key	General Data
Legacy Purchasing Document Number*	Company Code*	Purchasing Document Type*	Vendor Account Number*	Purchasing Organization*	Purchasing Group	Currency Key(ISO format)*
Ord_5	1710	NB	17386001	1710	001	USD
Ord_6	1710	NB	17386001	1710	001	USD

 

Item Data

EBELN

EBELP

PSTYP

KNTTP

MATNR

TXZ01

WERKS

LGORT

MATKL

WEPOS

WEUNB

REPOS

WEBRE

PCKG_NO

Key

General Data

Legacy Purchasing Document Number*

Item Number of Purchasing Document*

Item category

Account assignment category

Material Number

Short Text

Plant

Storage location

Material Group

Indicator: Goods Receipt

Indicator: Goods Receipt, Non-Valuated

Indicator: Invoice receipt

Indicator: GR-Based Invoice Verification

Package number

Ord_5

10

9

P

Material-1

1710

L001

X

X

X

X

1

Ord_6

10

9

P

Material-2

1710

L001

X

X

X

X

1

 

Account Assignment

EBELN	EBELP	ZEKKN	SAKTO	WBS_ELEMENT
Key
Legacy Purchasing Document Number*	Item Number of Purchasing Document*	Sequential Number of Account Assignment*	G/L Account Number	WBS Element
Ord_5	10	1	65008000	00000000000000000255TTO
Ord_6	10	1	65008000	00000000000000000255TTO

 

Create Comm. Structure  Acct A

EBELN	EBELP	PCKG_NO	LINE_NO	SERNO_LINE	PERCENTAGE	SERIAL_NO
Purchasing Document Number*	Item Number of Purchasing Document*	Package number*	Line Number*	Seq. Number of Acc. Assignment Specifica	Percentage for Account Assignment Value	Sequential Number of Account Assignment
Ord_5	10	2	2		100	1
Ord_6	10	2	2		100	1
Ord_6	10	2	3		100	1
Ord_6	10	2	4		100	1
Ord_6	10	2	5		100	1
Ord_6	10	2	6		100	1

 

Lines of Service Package

EBELN	EBELP	PCKG_NO	LINE_NO	EXT_LINE	OUTL_LEVEL	OUTL_IND	SUBPCKG_NO	QUANTITY	BASE_UOM	GR_PRICE	SHORT_TEXT
Purchasing Document Number*	Item Number of Purchasing Document*	Package number*	Internal line number*	Line Number	Hierarchy level of group	Indicator: Outline line	Subpackage number	Quantity with Sign	Base Unit of Measure	Gross price	Short Text
Ord_5	10	1	1		0	X	2
Ord_5	10	2	2	10	0			1,00	PC	400,20	Maintenance
Ord_6	10	1	1		0	X	2
Ord_6	10	2	2	10	0			1,00	PC	2 000,00	Job1 August 2020
Ord_6	10	2	3	20	0			1,00	PC	109,00	Job1 August 2020
Ord_6	10	2	4	30	0			1,00	PC	120,00	Job1 August 2020
Ord_6	10	2	5	40	0			1,00	PC	130,00	Job1 August 2020
Ord_6	10	2	6	50	0			1,00	PC	140,55	Job1 August 2020

 

7 Go throw migration steps. Couple Service Purchase Orders should be created at the and.



 

Now you have learned how to adjust Purchase Order migration object for Services. The same approach could be used for other service\limit business cases.

[former_member747126]

Hi Alexey,

We tested your test data, It does work to have unique EBELP 0010 and EBELP 0020 service lines, which is a great leap of progress. As expected the Net Price is resolved in this instance automatically. Though currently we are looking in to having them as well each EBELP 0010 and EBELP 0020 to have ≥ 2 service lines. We are looking in to that option currently.

Current steps attempted :
EKPO


ESKL

ESLL

This did not work, as well attempted initially with the internal line number in this layout. This gave the identical outcome as above

-Extra info for other readers: please note that it is best to copy paste data from tables of this Forum in an excel since this gives at times more correct numbers compared to the visual presentation without copy pasting-

Sincerely,

Sebastiaan

[former_member747126]

Hi all,

For those interested in having an Information rule on your Service Line in File Transfer LTMC,

this works with following information :

Source Structures :

On your S_ESLL add following:

Name      Data Type     Length  Column Header

INFORM   CHAR             1           Information Rule

Field Mapping :

T16_POSERVICES

S_ESLL Inform <= Move (S_ESLL-Inform)

Data input example :

Result:

Sincerely,

Sebastiaan

[former_member747126]

Hi Alexey,

I would like to inform that we found a way to have the more than one service line within one EBELP
ESLL

ESKL

EKPO






Sincerely,

Sebastiaan

[former_member726200]

Добрый день, можно поличить у вас нескоторую короткую консультацию по скайп Liudmila Yushkevich (Ashapir@mail.ru)

[S0021528162]

Hello Aleksey,

Do you have any solution for error: The overall limit is allowed only for enhanced limit items ?

I am trying to migrate open PO with K and B and I get this error.

Thank you in advance,

danielaT

[former_member772610]

Hi All,

For those interested in resolving the issue of the error message: "A FORM already exists with the name "_CONVERT_0001_".      "

This is resolvable with the following guide. https://www.youtube.com/watch?v=2JOXYG34OGA He was able to explain me what simple steps there were to take  in order to resolve this issue.

Sincerely,

Sebastiaan

[andrea2104]

Good morning,

Following your blog we are trying to create service POs with LMTC, but I received an error when I try to “Generate Runtime Object” in LTMOM:

Send below the excel files .xml and the details of the tcode LTMOM:

And than the structure T16 and T17

Could you tell me how to fix the error to generate the object correctly?

Thank you so much.

[alexey_danshin]

Hello Andrea.

Please try the following.

Br, Alexey.

alexey.danshin2

Blog Post Author

August 17, 2020 at 10:50 am

Hello Kiran.

If I have very strange errors in LTMOM I try to change Global Data by typing space. Then save object and Generate Migration Object. If no luck then please go Display Generated Function Group /1LT/SRQOLC_100000000000253 and try to analyze it.

Br,

Alexey.

[andrea2104]

Hy Alexey Thank you for your answer now works!

I have another problem with LTMOM\LTMC.

I added other two fields in LTMOM structures S_ESLL and S_EKPO:

• Service No. (ASNUM) in S_ESLL;


• Indicator for Service-Based Invoice Verification (LEBRE).

 

 

 

When I load the service order in LTMC the following error message appears: The activity number 3000015 does not exist

But activity number 3000015 exist. I try to create a PO with ME21N with same activity and works:

 

Which is the problem?

Thank you so much

[alexey_danshin]

Please try to pass 000000000003000015.

[andrea2104]

Ehi Alexey.

now works for all type of PO.

 

THX a lot.

[alexey_danshin]

Per favore.

[ckruegel]

Hi Alexey,

thank you very much for this very helpful tutorial / blog. I successfully implemented this project for our customer and generally it works fine! I have an additional question.

I want to migrate the actual quantity too. I added the fields "ESLL-ACT_MENGE" (Actual Quantity) and " ESLL-ACT_ WERT"(Actual Value) to source structure and  mapped the values by "MOVE-rule"

my problem is, the values were not migrated to target. Is there any chance to migrate this value to the target?

Thank you in advance
Carsten

[andrea2104]

Hi Guys.

I'm searching something like this blog without goal.

TOPIC: Migrating Service Purchase Agreement with S/4HANA Migration Cockpit.

 

Can you help me ?

THX a lot.