Skip to Content
author's profile photo Former Member
Former Member

BO Transportation Request ignored

Hello All,

A new attribute (INC_TRANSF_LOC_N) was created on the Selection Profile to filter data from "Freight Unit Stages" Windows in the cockpit.

But when cockpit is refreshed no data is filtered and a message is displayed, as described in the picture below.

I have checked the atributes for FU BO and the field INC_TRANSF_LOC_N doesn't appear in the option list.

Is there anyway to enable this filter for "Freight Unit Stages"? I have checked the atributes for FU BO and the field INC_TRANSF_LOC_N doesn't appear in the option list.

Regards,

Marcos.

Attributes.JPG (17.6 kB)
Attributes2.jpg (81.1 kB)
Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Apr 10, 2014 at 02:04 PM

    Hello Marcos,

    To filter FU you need to use /SCMTMS/TO. The criteria /SCMTMS/TR is to be user with TRQ.

    If you need to filter FUs (TOR) you need to use TO criteria.

    Best regards,

    Vicente Picardi

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Apr 10, 2014 at 04:18 PM

    Hello Marcos,

    We had the same requirement here in ArcelorMittal, to exclude from planning some incoterms and we have achieved it using BADI /SCMTMS/TRQ_SE_REQREQ to block for planning the OTR and propagating it to the FU.

    Rgs, Marcelo Lauria

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jun 05, 2014 at 07:00 AM

    Hi Marcos,

    What is your TM release? 9.0? For the message that "The field is in TRQ, is ignored in FU selection", can you please show the message number/class info? Because in my system, there is no such alerting message.

    From the message I guess the selection profile for FU doesn't support /SCMTMS/TR BO field filtering in standard logic, so this needs time to further investigation and I think this might need a lot of efforts to achieve the requirement from your side to support another BO field filtering for FU selection.

    However, there is another option that we can enhance the same field in FU root and introduce this new field in FU root to the selection profile for FU and the left thing is to synchronize the data between TRQ and FU for this field, and upon save of TRQ, we can syn-up the field value between TRQ and FU.

    For the existing data that the user will not do the action "Save", we can create a report for synchronization.

    Hope this helps.

    BR, Dawson

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.