SC with multiple attachments to PO

[Former Member]

Hi my friends!

I need your help, when I create a SC with more than 1 item and I attach files to the different items, the PO is created but ALL the attachments moved to de first PO item.

Example:

SC

ITEM 1

              DOC FILE ATTACHED

ITEM 2

            XLS FILE ATTACHED

PO

ITEM 1

              DOC FILE ATTACHED

              XLS  FILE ATTACHED

Please help me!!!

Thanks in advance!

Gax

[Former Member]

I'm working with SRM 5.5 & R3 4.6c!

[former_member183790]

Hi Gaston,

As a workaround, create a shopping cart with 2 different account assignments/2 different Product cat. and order the shopping cart, in the backend system PO will be created with 2 different line items and attachments will be transferred correctly based on the line items.

system combines the line items in the shopping cart based on the Product cat. and account assignment cat and transfer the same in to backend system.

BR

Santhosh

[Former Member]

More Screenshots!

[Former Member]

Hello Gaston,

It was great you shared the screen shots. Till SRM 7.0 EHP1 Service items get bundled whenever you create PO or PR from SC. I believe you may have some badi development to splitting them into two different line items in PO. That is the reason your attachment is bundling into one line item.

From EHP2 onwards service un-bundling feature is available please see Tridip's blog below which explain in details.

http://scn.sap.com/community/srm/blog/2012/08/29/adding-power-to-the-procurement-of-services-using-s...

Hope this helps.

Thank you
Ritesh

[Former Member]

Hi Gaston,

Thats fine, place a break point in BBP_CREATE_PO_BACK and see how the attachments are getting passed. If they are passed correctly out of SRM  then you might want to place a breakpoint in

bapi BAPI_PO_CREATE which will be called in ECC side of it to see how the attachments get transferred to ECC from SRM.

Regards,

Naveen

[Former Member]

SRM 5.5 & R3 4.6c

[Former Member]

Hello Gaston,

How did you guys have implemented separating two service line items (i.e. unbundling them) in PO creation? You could utilize the same thing for attachment whenever it transfer into PO.

Thank you

Ritesh

[Former Member]

Do you think that the problem is cause I'm using services?

[Former Member]

Hi Gaston,

Yeah... Please create Material item type shopping cart and test it out...

Thank you

Ritesh

[Former Member]

My friend,

                 The client create just POs from services items, but I tryied with RQs, SC with material items create RQs.

And the RQ is working fine!!

So I assume that I have problems with Services...

Where I can start to find??

Thanks in advance!

Gax

[Former Member]

Hello Gaston,

There must be a BADI BBP_CREATE_BE_PO_NEW being utilized to create Service Items separately instead of bundling the item as per standard. This is the same BADI i am referring you put screen shot for the attachment codes. Please include that inside your BADI logic which is un-bundling service items.

Hope this will help.

Thank you

Ritesh

[Former Member]

Hi Ritesh!

I understand that i need to start to use de PO_NEW BADI, but I have a lot of code into the PO_BACK.

Do you think that I can to move all the logic to the new one ?

Thanks in advance!

Gax

[Former Member]

Hello Gax,

PO_BACK BADI you are referring to BBP_CREATE_PO_BACK correct? The PO_NEW_BADI is updated BADI of PO_BACK one only. If you have already using that BADI you can take a look in code for Service items in there and update it with attachment logic as well.

Thank you

Ritesh

[Former Member]

My Friend,

                  I'm only using the BBP_CREATE_PO_BACK I will take a look there for service items.

Best Regards,

Gax

[Former Member]

Attached you can find more information!

[Former Member]

Hi,

I am assuming its Classic scenario.

Please see how it appears in the badi BBP_CREATE_BE_PO_NEW ( if you have implemented it) actually you need to this is where you need to tell it how to send the attachments to ECC .

The storage category, doc type and transfer active information is set here .

So check the badi and let us know if you see any thing strange with respect to attachments.

Regards,

Naveen

[Former Member]

Hi,

Please use the  function module BBP_PD_SC_GETDETAIL to see the attachment stored detials.

Inside this you can see,

BBP_CREATE_PO_BACK BADI,

CT_ATTACH_BE -> "KW Attachments Including Document

CV_ATTACH_BE_DOC_TYPE ->"Document Type for DMS in the Backend System

CV_ATTACH_BE_STORAGE_CAT

CV_ATTACH_TRANSFER_ACTIVE -> "Activate Transfer of Attachments

CV_ATTACH_USE_URL -> "Transfer URL Instead of the File

CV_INTERNAL_ATTACH_NO_TRANSFER ->"Do not Transfer Internal Attachments

CV_INTERNAL_ATTACH_BE_DOC_TYPE ->"Individual Document Type in DMS for Intern

Regards,

Naga.

[Former Member]

Hi Naveen!

I have implemented the BADI BBP_CREATE_PO_BACK, the code is the following:

  cv_attach_BE_DOC_TYPE = 'SRM'.

  cv_attach_TRANSFER_ACTIVE = 'X'.

  cv_attach_BE_storage_cat = 'DMS_C1_ST'.

When I tried to implement BBP_CREATE_BE_PO_NEW, the BADI CREATE_PO_BACK stoped to work.

Thanks!

[Former Member]

HI,

Please check your customization settings as mentioned below.

If you wish to store shopping cart attachments in the back-end system, you must first activate the data transfer by creating an active method in the Business Add-Ins (BAdIs) BBP_CREATE_BE_PO_NEW (for purchase orders)

Procedure:

You have to configure the back-end Document Management System (DMS) in transaction DC10:

1.Create document type SRM. Note that no flag is set in any of the columns.

2.Double-click in the detail view to define the new Doc. type desc. = SRM Documents. Set the Use KPro indicator.

    Enter 1 in the Number assignment field.

    Enter an internal number range interval. You can use an existing interval or create a new one in transaction CV90. The internal number range must be used, because the GUID of the SAP SRM attachments has more digits than the number in the back-end system.

    Maintain the number exit. The number exit is a program exit for document numbers. It controls number assignment and version numbering for documents. The default setting is MCDOKZNR. If you want to control the number assignment or the version increment via a USER_EXIT, then you have to replace the program MCDOKZNR with a company-specific program. You can find further information in the field help for number exit.

    In the screen area Field selection, enter – in the Document Status field.

3.Go to the dialog structure and double-click the entry Define object links. Define the new object links EKPO and EBAN. Maintain object link descriptions for EKPO (Purchase order item; Scr.no. 248) and EBAN (Purchase req. item; Scr. no. 247)

4.Define the workstation application in transaction DC30.

Regards,

Naga.

[Former Member]

Hi !! Thanks for quick response!

I have everything configured, I can not to use BBP_CREATE_BE_PO_NEW cause when I activate that, BBP_CREATE_PO_BACK stop to working and 3000 ABAP code lines are there!

SC attachments is tranfer to PO but all the files to the first item of the PO.

Thnaks!

Gax