<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>Question Re: Packspec determination with OBDL using Sold to/Route/Pack profile field combination in Supply Chain Management Q&amp;A</title>
    <link>https://community.sap.com/t5/supply-chain-management-q-a/packspec-determination-with-obdl-using-sold-to-route-pack-profile-field/qaa-p/11625228#M160924</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Vijay&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You must implement the BADi to populate the value. I used it and worked for me.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Jobi&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 03 May 2016 12:13:42 GMT</pubDate>
    <dc:creator>jobi_t</dc:creator>
    <dc:date>2016-05-03T12:13:42Z</dc:date>
    <item>
      <title>Packspec determination with OBDL using Sold to/Route/Pack profile field combination</title>
      <link>https://community.sap.com/t5/supply-chain-management-q-a/packspec-determination-with-obdl-using-sold-to-route-pack-profile-field/qaq-p/11625224</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P style="margin-bottom: .0001pt;"&gt;&lt;SPAN style="font-size: 12pt; font-family: 'inherit',serif;"&gt;Hi All,&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="margin-bottom: .0001pt; font-weight: inherit; font-style: inherit;"&gt;&lt;SPAN style="font-size: 12pt; font-family: inherit, serif;"&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P style="margin-bottom: .0001pt; font-weight: inherit; font-style: inherit;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="font-family: inherit, serif;"&gt;We have a requirement to determine Packspec using Sold to/Route/Pack profile combination during WO creation.A custom&lt;/SPAN&gt;&lt;SPAN style="font-weight: inherit; font-style: inherit;"&gt; &lt;SPAN style="font-family: inherit, serif;"&gt;condition table was created copying the standard OBDL condition type/access sequence.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="margin-bottom: .0001pt; font-weight: inherit; font-style: inherit;"&gt;&lt;SPAN style="font-size: 12pt;"&gt;&lt;SPAN style="font-style: inherit; font-family: inherit, serif; font-weight: inherit;"&gt;Though we have the sold to &lt;/SPAN&gt;&lt;SPAN style="font-family: inherit, serif;"&gt;field&lt;/SPAN&gt;&lt;SPAN style="font-weight: inherit; font-style: inherit;"&gt; &lt;SPAN style="font-family: inherit, serif;"&gt;PAK_SOLD_TO in the field &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN style="font-family: inherit, serif;"&gt;catalogue&lt;/SPAN&gt;&lt;SPAN style="font-weight: inherit; font-style: inherit;"&gt; &lt;SPAN style="font-family: inherit, serif;"&gt;and was able to add this to the condition table. The system is unable to consider this field during packspec determination because the open task table /SCWM/ORDIM_O do not have sold to field.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="margin-bottom: .0001pt; font-weight: inherit; font-style: inherit;"&gt;&lt;SPAN style="font-size: 12pt; font-family: inherit, serif;"&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P style="margin-bottom: .0001pt; font-weight: inherit; font-style: inherit;"&gt;&lt;SPAN style="font-size: 12pt; font-family: inherit, serif;"&gt;Is there anyway to determine the packspec using the fields mentioned during the WO creation.Any suggestion will be much appreciated.&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="margin-bottom: .0001pt; font-weight: inherit; font-style: inherit;"&gt;&lt;SPAN style="font-size: 12pt; font-family: inherit, serif;"&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P style="margin-bottom: .0001pt; font-weight: inherit; font-style: inherit;"&gt;&lt;SPAN style="font-size: 12pt; font-family: inherit, serif;"&gt;Many thanks.&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="margin-bottom: .0001pt; font-weight: inherit; font-style: inherit;"&gt;&lt;SPAN style="font-size: 12pt; font-family: inherit, serif;"&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P style="margin-bottom: .0001pt; font-weight: inherit; font-style: inherit;"&gt;&lt;SPAN style="font-size: 12pt; font-family: inherit, serif;"&gt;Kind Regards&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="margin-bottom: .0001pt; font-weight: inherit; font-style: inherit;"&gt;&lt;SPAN style="font-size: 12pt; font-family: 'inherit',serif;"&gt;Vijay&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 02 May 2016 08:06:50 GMT</pubDate>
      <guid>https://community.sap.com/t5/supply-chain-management-q-a/packspec-determination-with-obdl-using-sold-to-route-pack-profile-field/qaq-p/11625224</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2016-05-02T08:06:50Z</dc:date>
    </item>
    <item>
      <title>Re: Packspec determination with OBDL using Sold to/Route/Pack profile field combination</title>
      <link>https://community.sap.com/t5/supply-chain-management-q-a/packspec-determination-with-obdl-using-sold-to-route-pack-profile-field/qaa-p/11625225#M160921</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Vijay,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;warehouse order ( WO ) is an executable package and can contain one 'or' more WTs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;while creating the WT it self , WO also can be created.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;system can be created WTs and&amp;nbsp; WO ( executable package )&amp;nbsp; wrf to the outbound delivery order.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if you are trying to generate auto pick HU against WO, check the relevant setup is maintained in the packspec.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And also check the access sequence against your condition table , how access types &amp;amp; priorities are maintained.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BR,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;C K Reddy&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 02 May 2016 10:43:11 GMT</pubDate>
      <guid>https://community.sap.com/t5/supply-chain-management-q-a/packspec-determination-with-obdl-using-sold-to-route-pack-profile-field/qaa-p/11625225#M160921</guid>
      <dc:creator>former_member183610</dc:creator>
      <dc:date>2016-05-02T10:43:11Z</dc:date>
    </item>
    <item>
      <title>Re: Packspec determination with OBDL using Sold to/Route/Pack profile field combination</title>
      <link>https://community.sap.com/t5/supply-chain-management-q-a/packspec-determination-with-obdl-using-sold-to-route-pack-profile-field/qaa-p/11625226#M160922</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi C K Reddy,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you for your reply.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yes, I am trying to generate auto pick HU during WO creation, for the combination for Route/Pack profile/Sold to party.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The required configuration is set up as mentioned by you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The WOCR is maintained with the pack profile and Route is flowing into the WT, so we are perfectly able to determine the packspec condition with route/pack profile combination.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, we are not able to determine the packspec with sold to/route/pack profile combination because the system is unable to retrieve sold to value from the WTs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there any way to determine the sold to values from the WTs during the packspec determination.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards,&lt;/P&gt;&lt;P&gt;Vijay&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 May 2016 11:35:35 GMT</pubDate>
      <guid>https://community.sap.com/t5/supply-chain-management-q-a/packspec-determination-with-obdl-using-sold-to-route-pack-profile-field/qaa-p/11625226#M160922</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2016-05-03T11:35:35Z</dc:date>
    </item>
    <item>
      <title>Re: Packspec determination with OBDL using Sold to/Route/Pack profile field combination</title>
      <link>https://community.sap.com/t5/supply-chain-management-q-a/packspec-determination-with-obdl-using-sold-to-route-pack-profile-field/qaa-p/11625227#M160923</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Vijay,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;it would required to implement the BADI, if we are adding additional fields in filed catalog to determine packaging specification.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;here is one BADI ' /SCWM/EX_PS_DET_PREPARE ' is available.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;for more clarity , please go through the below path.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SCM Extended Warehouse Management-Extended Warehouse Management-Master Data-Business Add-Ins for Packaging Specifications-Packaging Specification Determination&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IMG documentation against this BADI as below.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;EM style="text-decoration: underline;"&gt;If you add additional fields to the packaging specification field catalogue, the determination data for this new fields can be completed.&lt;/EM&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BR,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;C K Reddy&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 May 2016 11:53:43 GMT</pubDate>
      <guid>https://community.sap.com/t5/supply-chain-management-q-a/packspec-determination-with-obdl-using-sold-to-route-pack-profile-field/qaa-p/11625227#M160923</guid>
      <dc:creator>former_member183610</dc:creator>
      <dc:date>2016-05-03T11:53:43Z</dc:date>
    </item>
    <item>
      <title>Re: Packspec determination with OBDL using Sold to/Route/Pack profile field combination</title>
      <link>https://community.sap.com/t5/supply-chain-management-q-a/packspec-determination-with-obdl-using-sold-to-route-pack-profile-field/qaa-p/11625228#M160924</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Vijay&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You must implement the BADi to populate the value. I used it and worked for me.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Jobi&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 May 2016 12:13:42 GMT</pubDate>
      <guid>https://community.sap.com/t5/supply-chain-management-q-a/packspec-determination-with-obdl-using-sold-to-route-pack-profile-field/qaa-p/11625228#M160924</guid>
      <dc:creator>jobi_t</dc:creator>
      <dc:date>2016-05-03T12:13:42Z</dc:date>
    </item>
  </channel>
</rss>

