JR51920: Enhancement of requisition list upload

APAR status

• Closed as new function.

Error description

• The current requisition list function not support the
  participant role user to load items, the display page is also
  not respect the participant role setting.
  

Local fix

Problem summary

• USERS AFFECTED:
  The customer can not using the requisition list when using the
  participant role of another org.
  
  PROBLEM ABSTRACT:
  Enhancement of requisition list upload
  
  BUSINESS IMPACT:
  Will effect the customer for the requisition list upload
  function
  
  RECOMMENDATION:
  

Problem conclusion

• For loading data with participant role
  
  1: The contract Id is always passed to the scheduler whatever
  the store front setting.This contract id is fetched from the
  context,As this contract id is fetched from the context and
  there already did the validation, we will not validate here and
  directly pass it to the scheduler job.
  
  2: The Org id will be passed to the scheduler side only when the
   current user is under another org with a participant role. This
   org id is fetched from the context, and we will compare the org
   id in the context with the user's org id, if they are the same,
   we will do nothing, if they are different ,we will pass it to
  the scheduler job.
  
  Both 1 and 2 will be done in the create command.
  
  3: When run the scheduler job, we will clone the context and get
   the contract id and org id we passed. Then if the passed the
  org id is not null, we will check if the current user have a
  participant role of the passed org id, if it is true, we will
  set this id to the cloned context and clear the context's
  trading id.
  
  4: After checking the org id, we will check the passed contract
  id, we will check if the passed contract id is an eligible
  contract for the user and the org in the cloned context(already
  set the right org id in step3), then if it is a valid contract ,
   we will set this contract id to the current trading id in the
  cloned context. This will make the context have the correct
  contract id setting.
  
  5: Then using the cloned context to do the entitlement check and
   orders creation.
  
  
  For the display load tasks by participant role id.
  1: Inherited the FetchFileUploadJobCmdImpl command, and register
   this command in CMDREG with the below interface.
  com.ibm.commerce.content.facade.server.commands.FetchFileUploadJ
  obCmd/FileUploadJob[NumberOfDays= and UploadType=]
  
  2: In the new command, override the performExecute() and check
  the fetch noun, to see if the org id in that column is equal
  with the id in the context. If equal, then return this noun, if
  not, do not return.
  
  3: When upload the file, I make a change to record an
  organization id in the properties column of UPLOADFILE table.
  This is used to do check in step2.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WC BUS EDITION

• Fixed component ID

  5724I3800

Applicable component levels

• R700 PSY

     UP