java.lang.Object
de.hybris.platform.sap.sapordermgmtbol.transaction.salesdocument.backend.impl.erp.strategy.IncompletionMapperImpl
All Implemented Interfaces:
IncompletionMapper

public class IncompletionMapperImpl extends Object implements IncompletionMapper
Maps the incompletion log from ERP SD to BOL messages during LO-API read
  • Field Details

    • FIELD_HEADER

      protected static final String FIELD_HEADER
      Message refers to header level
      See Also:
    • FIELD_CFG

      protected static String FIELD_CFG
      Indicates: Issue is related to product configuration
    • MSG_CLASS_INCOMPLETION

      protected static String MSG_CLASS_INCOMPLETION
      Dummy message class for incompletion messages
  • Constructor Details

    • IncompletionMapperImpl

      public IncompletionMapperImpl()
  • Method Details

    • mapLogToMessage

      public void mapLogToMessage(com.sap.conn.jco.JCoTable incompLog, com.sap.conn.jco.JCoTable messages, ItemList items)
      Description copied from interface: IncompletionMapper
      Copies the incompletion log to the table of messages which can be processed further on.
      Specified by:
      mapLogToMessage in interface IncompletionMapper
      Parameters:
      incompLog - JCO Table of incompletion messages
      messages - Standard message table
      items - Sales document items
    • mapItemMessage

      protected void mapItemMessage(com.sap.conn.jco.JCoTable incompLog, com.sap.conn.jco.JCoTable messages, ItemList items)
      Map incompletion message on item level. Messages on sub item level will not be considered.
      Parameters:
      incompLog - JCO table of incompletion log, data will be read from current record
      messages - JCO table of messages, data will be written into current record
      items - Sales document items
    • mapAttributes

      protected void mapAttributes(com.sap.conn.jco.JCoTable incompLog, com.sap.conn.jco.JCoTable messages)
      Maps attributes between incompletion log and messages. The data written to the message table must match the message mapping customizing in messages.xml
      Parameters:
      incompLog - JCO table of incompletion log, data will be read from current record
      messages - JCO table of messages, data will be written into current record
    • considerLogEntry

      protected boolean considerLogEntry(String fieldName)
      Do we consider this entry in the incompletion log? This depends on entry in FDNAM, the standard implementation only takes care of issues related to CUOBJ
      Parameters:
      fieldName -
      Returns:
      Do we process this entry?
    • isHeaderLevel

      protected boolean isHeaderLevel(String fieldHeader)
      Checks: Message is on header level
      Parameters:
      fieldHeader -
      Returns:
      Header level?
    • getBackendUtil

      public BackendUtil getBackendUtil()
      Returns:
      the backendUtil
    • setBackendUtil

      public void setBackendUtil(BackendUtil backendUtil)
      Parameters:
      backendUtil - the backendUtil to set