cancel
Showing results for 
Search instead for 
Did you mean: 

Inernal note transfer

Former Member
0 Kudos

hi...

i am using classic scenario....SRM 4.0

I want to transfer the text from SC to PO in backend system....

I know the BAdi...

what are the things to be mantained.....

thx..

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

thx...

lisa_sheil
Contributor
0 Kudos

Hi,

-> If it is the Internal Note or Vendor text that you wish to transfer please review the following:

It is hard coded that the internal note texts are transferred to the

RQ / PO info record note. This internal note has the customizing

TextID F05.

You can check the entries in your R/3 Backend customizing as follows:

Menu path>SPRO>IMG>Materials Management>Purchase Order>

Texts for purchase orders> Define Text Types for Item Texts:

Value: 01 "Item text"

Value: 05 "Infor record note"

The standard text-id are for Purchase requisition

B01 = item text

B02 = item note

for Purchase order

F01 = item text

F05 = internal note from EBP

These are default values. Because of performance reasons (an additional

RFC Call to Backend to check this) the values are hardcoded.

If you want to user other textid than the default, you can change this

in the BADI BBP_CREATE_PO_BACK or BBP_CREATE_REQ_BACK

Please check EBAN table because the error can be in Backend system.

ITXT text in BBP syst is the Vendor Text and should be transfered to B01

NOTE text in BBP syst is the Internal Note and should be transfered

to B02.

-> If it is the longtext please review the following:

From SRM side we can map the long text fields with BAPI

structure (which is not available in lower releases), inorder to map

this we have to use BBP_LONGTEXT_BADI > GET_COPY_RULES

method. This will be used to map the long text fields with

BAPI structure as per the copy rules defined in the method

GET_COPY_RULES.

Now when we transfer the PO the long text fields (potextitem) would be

available in R/3 system but this 'potextitem' should be mapped with

the bapi_potextitem in R/3 side. Inorder to map this we have to use the

BADI BBP_POINBOUND_BADI > MAP_BEFORE_BAPI method. In

MAP_BEFORE_BAPI method (of the BADI BBP_POINBOUND_BADI) we need to map

the structure BAPI_POTEXTITEM with the values from the structure

bbp_poitemtext.There is no need of RFC call to SRM system from R/3

system inorder to get the long text vlalues.

Here we have to use both the BADIs (BBP_LONGTEXT_BADI in SRM side,

BBP_INBOUND_BADI in R/3 side) to transfer the vendor text and internal

notes.

i) BBP_LONGTEXT_BADI > used to map the long text fields

to BAPI strcture based on the copy rules (defined in the

method GET_COPY_RULES).

ii)BBP_INBOUND_BADI > used to map the long text with

BAPI_POTEXITEM which is available in R/3 system. RFC call

to SRM is not required which would lead to performance

issues

I hope this helps,

Kind Regards,

Lisa

Former Member
0 Kudos

Hi,

following links could be helpful..

989184 Transferred shopping cart with internal attachments

1057932 FAQ: Atachment transfer to backend, Required Configurations

916347 Transfer shopping cart with internal attachments

Thanks

prasad.s

Former Member
0 Kudos

hi...

i am not asking for attachment transfer....

my doubt is about text transfer (internal text)from SRM to R/3.....

thanks...