po output form determination

[Former Member]

Hi,

    i am workign on SRM 7 extended classic scenario. i need to configure SRM po output in such a way that system should pick po form by company code or by plant..every company code has different logo and terms and conditions that should be printed every time.purchase orders are created automatically soon shopping cart is approved.can some one advise how this can be achieved.we are using smartforms.

Thanks,

[Former Member · Accepted solution]

Any Thoughts Guys ?

[Former Member · Accepted solution]

Hi Iqbal,

There is a BADI BBP_OUTPUT_CHANGE_SF which can be used to pick up different smartform layouts as per the Company Code.

Please check with your ABAPer and let me know if it works.

Br,

Raghu

[Former Member · Accepted solution]

Thanks Raghu.i am working with my development team.will update you soon about the results.

[Former Member · Accepted solution]

Raghu,

          i need some forms in english and some other in spanish.how to change smartfrom language in spanish.furthermore is there any configuration required in SPRO to use Multiple Smartforms based on company code.please advice

[Former Member · Accepted solution]

Q) i need some forms in english and some other in spanish.how to change smartfrom language in spanish

-> I am afraid, it is not be possible to maintain different languages for a smart form.

However, we had a similar requirement to print the texts based on the vendor language and we did that by maintaining the translation texts in a Custom table.

(This is my personal opinion, I would suggest you to validate this with your developer, as I am a functional consultant)

Q) is there any configuration required in SPRO to use Multiple Smartforms based on company code.please advice

->  No this is not possible, that is the reason I have suggested the BADI which is used exclusively to pick up smart form based on the company code.

Please let me know whether the BADI worked or not ?

Thanks,

Raghu

[Former Member · Accepted solution]

Thanks Raghu for Quick reply.i am still confuse let me explian in bit detail

1) SRM is up and runnng for English version.po output triggers fine and can be downloaed in PDF version

Requiremnt.

Po output should be in spanish for newly created compnay codes.each comapny code has different logo.(DO i need to ask developer to create saperate form for each company code.if yes in SPRO i can attach only one Form per action profile.how to achieve it.)

How to develpe smartform in Spanish language.what do i need to tell the ABAPER.what are the steps i need to perform in order to generate purchase order outputs in spanish for three diferent company codes.

Thanks in Advance.

[Former Member · Accepted solution]

Q) Po output should be in spanish for newly created compnay codes.each comapny code has different logo.(DO i need to ask developer to create saperate form for each company code.if yes in SPRO i can attach only one Form per action profile.how to achieve it.)

-> I you create a separate SF (Smart form) for Spanish language, you can use the BADI BBP_PO_CHANGE_SF to call the newly created SF for the Spanish Company Code.

In SF, there is a functionality called "Conditions" to validate the Organizational/Runtime values in PO for example: Company Code, based on which certain logic would work.

Please ask your ABAPer to use this to call a different logo as per the company code. This way you can have a single SF and accommodate multiple logos

----------------------------------------------------------

Q) How to develpe smartform in Spanish language.what do i need to tell the ABAPER.what are the steps i need to perform in order to generate purchase order outputs in spanish for three diferent company codes.

- > Developing a SF in Spanish is no different from English.

SF simply populates the data from the tables and the runtime values of the Purchasing document, the only thing that would be different is the static fields/labels.

Meaning instead of having the labels/texts "Item Number"/"Delivery Address"/"Invoice Address"/.....etc in the SF layout your ABAPer would maintain the same text in Spanish.

You can ask them to use the same logic which has been implemented for SF which is created in English to populate the fields. (Unless there is a difference in which the fields have to be populated)

----------------------------------------------------------

Please let me know if anything is unclear and I feel we are diverting from the actual discussion that is to call different SF per CC which can be accomplished using the BADI which I mentioned.

If that is clear, please mark this thread as answered and open another one probably in the ABAP area if you have any development related questions.

Thanks,

Raghu.

[oliver_wurm]

Hi IQBAL,

you can use an implementation of BADI BBP_PROCESS_PO. This replaces (if implemented) the standard smartform call.

Maybe the following code example helps:

<code to find out what Smartform is desired >

* get the function name for this smart form

   CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'

     EXPORTING

       formname           = <Smartform found in initial step>

     IMPORTING

       fm_name            = lv_function_name

     EXCEPTIONS

       no_form            = 1

       no_function_module = 2

       OTHERS             = 3.

   if sy-subrc ne 0.

      cv_smartrc = sy-subrc.

      exit.

   endif.

*

   CALL FUNCTION lv_function_name

     EXPORTING

       archive_index_tab    = ct_archive_index_tab

       archive_parameters   = is_archive_parameters

       control_parameters   = ls_control_parameters

       mail_appl_obj        = is_mail_appl_obj

       mail_recipient       = is_mail_recipient

       mail_sender          = is_mail_sender

       output_options       = is_output_options

       user_settings        = ip_user_settings

       sf_po                = is_sf_po

     IMPORTING

       document_output_info = es_document_output_info

       job_output_info      = es_job_output_info

       job_output_options   = es_job_output_options

     EXCEPTIONS

       formatting_error     = 1

       internal_error       = 2

       send_error           = 3

       user_canceled        = 4

       OTHERS               = 5.

   cv_smartrc = sy-subrc.

Regards

Oliver