cancel
Showing results for 
Search instead for 
Did you mean: 

Add customer fields in Shopping cart and purchase order

0 Kudos

Hi,

I have to add fields(moder of transport, country origin, country destination and more) in Shopping cart and purchase order in SRM system and remotle i have to update the same data in R/3 System.

could you please guide how to add the fields in screen.

regards

Shakeer

Accepted Solutions (0)

Answers (7)

Answers (7)

0 Kudos

Hi atul,

thanks for your input i hope you understood my requirement.

i am new in SRM TECH.

in BBP_CUF_BADI_2 i created the implementation, and selected the method MODIFY_SCREEN.

could you guide me how to refer the strucre field like ZZEXPVZ for shopping cart and po.

how to make visible the above field in standard screen.

could you give me sample code.

method IF_EX_BBP_CUF_BADI_2~MODIFY_SCREEN.

endmethod.

Regards

shakeer

yann_bouillut
Active Contributor
0 Kudos

Hi,

Table ET_FIELDS, XINPUT = 'X' and XDISPLAY = 'X'.

Please check SAP note 672960.

Kind regards,

Yann

Former Member
0 Kudos

Dear All,

Can we add customer field in the Carry out sourcing "worklist" and "find" screen , example for: PR number and tracking number (PDP scenario) ?

Can we also use Badi BBP_CUF_BADI_2 for this purpose ? Can anyone please also describe about transaction SHD0 ?

Thanks and Regards

Darwin

Former Member
0 Kudos

Hi

Please find the sample code below.

<b>By default, all the customer fields are visible on the document and are Input-enabled.</b>

METHOD if_ex_bbp_cuf_badi_2~modify_screen.

*-- To make the custom fields either invisible / display only / Input Disabled/Display Disabled.

*--- Data declaration
  DATA                ls_et_fields TYPE bbps_cuf_display.


*-- Hiding the fields Validity Start Date and End Date
      LOOP AT et_fields INTO ls_et_fields.

        CASE ls_et_fields-fieldname.
*---- Lease Validity Start Date - Input/Display Disabled.
          WHEN 'ZZLEASE_SDATE'.
            ls_et_fields-xdisplay = space.
            ls_et_fields-xinput   = space.
            MODIFY et_fields FROM ls_et_fields
                   TRANSPORTING xdisplay xinput.
            CLEAR ls_et_fields.
*---- Lease Validity End Date - Input/Display Disabled.
          WHEN 'ZZLEASE_EDATE'.
            ls_et_fields-xdisplay = space.
            ls_et_fields-xinput   = space.
            MODIFY et_fields FROM ls_et_fields
                   TRANSPORTING xdisplay xinput.
            CLEAR ls_et_fields.
        ENDCASE.

      ENDLOOP.


ENDMETHOD.

Let me know incase you still have any issues.

Regards

- Atul

0 Kudos

Hi,

i created the following structure and the required fields as per the SAP note.

CI_BBP_HDR,

CI_BBP_HDR_PO,

CI_BBP_HDR_SC,

CI_BBP_ITEM,

CI_BBP_ITEM_PO,

CI_BBP_ITEM_SC.

Now i want to add the feilds in the screen.

Which BADI i need take..

i tried the links, recieved so far.

Regards

Shakeer

Former Member
0 Kudos

Hi

We have done this type of requirement several times in our previous SRM Implementations.

<b>You need to create an Append Structure in the Standard Structure to create the custom fields in your case.</b>

<u>Refer this link below for details.</u>

http://help.sap.com/saphelp_47x200/helpdata/en/cf/21eb61446011d189700000e8322d00/frameset.htm

<b>Define the fields of the append structure. You can proceed as when creating a normal structure with two restrictions (see Creating Structures).

The fields of an append structure must lie in the customer namespace, that is the field names must begin with ZZ or YY. This prevents conflicts with fields inserted in the table by SAP.</b>

http://help.sap.com/saphelp_srm50/helpdata/en/5b/c9df3b6ac34b44e10000000a114084/frameset.htm

http://help.sap.com/saphelp_srm50/helpdata/en/28/857a1867b52e4f8472c5d49209a675/frameset.htm

<u>BBP_CUF_BADI_2 BADI will be used to control the properties (hide/unhide, input/output enable or disable) for those customer fields you created in the above append structures.

BBP_DOC_CHANGE_BADI for defaulting or modifying the customer field contents, incase required.

BBP_DOC_CHECK_BADI for issuing customer messages for the customer field contents (incase data is entered incorrectly) , incase required.</u>

Let me know incase you face any issues.

Regards

- Atul

0 Kudos

i have gone through the SAP Note Number 458591 and created the fields and structrue at item and header...

Do I need to create separate sub screen and add this field to the screen?

I have the requirement I need to add this fields in existent screen.

I checked the BAdI BBP_CUF_BADI/BAdI BBP_CUF_BADI_2.

I hope this BADI help us to write the logic, I need help on how to create the fields.

Regards

Shakeer Ahmed.

yann_bouillut
Active Contributor
0 Kudos

Hi,

You don"t need to create sub screen

SC Item CUF are automatically added to basic data screen and header CUF are added above the approval note.

You don"t choose where you want to add the CUF in SRM.

However in ECC, you can choose where you want to add your CUF . For this follow Ramki comments.

Kind regards,

Yann

Former Member
0 Kudos

Hi

It's quite easily possible to add customer fields on the SC - Header / Item level.

Please refer to the following links ->

Pls refer to the following OSS Notes

<u>458591 - User-defined fields: Preparation and use

672960 - User-defined fields 2</u>

This contains all the required information what you need to do for the custom fields.

Hope this will definitely help.

Regards

- Atul

0 Kudos

May i have example

yann_bouillut
Active Contributor
0 Kudos

Hi,

Example :

CUF at SC header level:

You have to append in SE11 your Zfield in

INCL_EEW_PD_HEADER_CSF_SC

AND

INCL_EEW_PD_HEADER_CSF

The Zfield will appear in the Step3 screen above the "approval note"

kind regards,

Yann

yann_bouillut
Active Contributor
0 Kudos

Hi,

You can read my answer here :

Kind regards,

Yann

Ramki
Active Contributor
0 Kudos

Hi

You need customer fields and update the same data in R/3 PO also:

Customer fields in SRM

1) Follow as Yann mentioned. It is easy and well explained in note 672960.

Check R/3 PO for existence of these fields

1) Hope you have these fields maintained in R/3 (are they additional customer fields there too). If you do not have them yet, pl check user exit MM06E005; you will need good ABAPer.

Transfer the field values from SRM to R/3

1) Check the thread which explains (you will need ABAPer here too).

Best regards

Ramki

yann_bouillut
Active Contributor
0 Kudos

Hi,

Everything is explained in OSS notes 458591 and 672960

Kind regards,

Yann

Former Member