I_SALESORDINDELIVTRDCMPLNCISS

CDS View

SOFM Trade Compliance Issue In Delivery

I_SALESORDINDELIVTRDCMPLNCISS is a CDS View in S/4HANA. SOFM Trade Compliance Issue In Delivery. It contains 1 fields. 1 CDS views read from this table.

CDS Views using this table (1)

ViewTypeJoinVDMDescription
C_DelivDocItemTrdCmplncIssue view inner CONSUMPTION Delivery Doc Item Trade Compliance Issue

Fields (1)

KeyField CDS FieldsUsed in Views
DueDays DueDays 1
@ClientHandling.algorithm: #SESSION_VARIABLE 
@ObjectModel.usageType.dataClass: #MIXED
@ObjectModel.usageType.serviceQuality: #D
@ObjectModel.usageType.sizeCategory: #S

@EndUserText.label:  'SOFM Trade Compliance Issue In Delivery'
@VDM.viewType: #COMPOSITE
@AccessControl.authorizationCheck: #CHECK
@AbapCatalog.sqlViewName: 'ISOFISSUEDE07'
@AbapCatalog.compiler.compareFilter: true
@AbapCatalog.preserveKey: true
/*
-------------
Description:  --AT23.9.2019 Trade Compliance Issue DE07 CE2002

Detects  Deliveries with Trade Compliance issue. An issue exists when at least one of the following areas
Embargo, Legal Control or Watch List Summary is "Decision Pending" (=B) or "Blocked" (=C).
The issue is solely detected on item level (the issue is semantically related to delivery items).

The basis of the due date calculation, is the next action/step that is not performed due to the issue.
For issues in delivery this due date logic is alway the same.

Note (added 27.9.2019 by AT):
  - all item status (that were missing in P_SalesOrderInDelivDueDate) now also in P_SalesOrderInDelivDueDate, so
    P_SalesOrderInDeliv_ITM_DueDate now replaced by  P_SalesOrderInDelivDueDate
  - P_SalesOrderInDeliv_ITM_DueDate is nowhere used anymore !
*/

--AT11.08.2020 for all issues: VBKD-BSTKD (PurchaseOrderBYCustomer) no longer provided by issues (no true hdr attribute & too expensive)

define view I_SalesOrdInDelivTrdCmplncIss
//with parameters

//  @Consumption.hidden: true

//  @Environment.systemField: #SYSTEM_DATE

//  P_ReferenceDate : sydate

as select distinct from  P_SalesOrderInDelivDueDate --P_SalesOrderInDelivItmDueDate  --AT27.09.2019 use non-item version instead
{
  //Key

  key SalesOrder,        
  key DeliveryDocument,     
  key DeliveryDocumentItem,
                    
  //Issue

  cast('DE07'as issue_sof)   as Issue,
  cast('20_DE' as issue_cat) as IssueCategory,       

  @DefaultAggregation: #MIN
  cast(Dats_Days_Between( cast($session.system_date as dats), DueDate ) as due_days) as DueDays,      
  
  //Counter

  --cast(1 as ITEMS_IN_DELIVERY) as NmbrOfItemsInDelivery,  
  cast( cast( 1 as abap.int4 ) as items_in_delivery )  as NmbrOfItemsInDelivery,
        
  //Organization

  SalesOrganization,
  DistributionChannel,
  OrganizationDivision,
  
  //Misc

   RequestedDeliveryDate,
   OverallSDProcessStatus,
   SalesDocumentDate,
   SalesGroup,
   SalesOffice,
   SoldToParty,
   --PurchaseOrderByCustomer,
  
  //Category

  SalesDocumentType as SalesOrderType    
   
}

where
  ( 
--  Update 19.05.2021 from Thorsten Refior:  for all three topics a further value (D, D, D) has to be considered  
  TrdCmplncEmbargoSts       = 'B' or TrdCmplncEmbargoSts       = 'C'  or  TrdCmplncEmbargoSts       = 'D' or
  TrdCmplncSnctndListChkSts = 'B' or TrdCmplncSnctndListChkSts = 'C'  or  TrdCmplncSnctndListChkSts = 'D' or
  TrdCmplncLegalControlSts  = 'B' or TrdCmplncLegalControlSts  = 'C'  or  TrdCmplncLegalControlSts  = 'D'
   ) and  
  (GoodsMovementStatus = 'A'      or GoodsMovementStatus       = 'B' )

 /*+[internal] {
"BASEINFO":
{
"FROM":
[
"P_SALESORDERINDELIVDUEDATE"
],
"ASSOCIATED":
[],
"BASE":
[],
"ANNO_REF":
[],
"SCALAR_FUNCTION":
[],
"VERSION":0,
"ANNOREF_EVALUATION_ERROR":""
}
}*/