Import Transactional Data into DataHub

Options
joseantonio.galindo
joseantonio.galindo Member, ALL USERS, Community Member, Certified Model Builder Posts: 5 Contributor
in Extensibility

Dear Community, 

 

I have a question related to import transactional data (Net Sales) into Data Hub, with the following requirements:

  • The Net Sales and Qty Volumes are grouped by more than 10 attributes required for Sales Planning Purposes. Best practices in Anaplan is to concatenate those attributes that will be the key for the line items, but in this case are more than 10 attributes so I think is not a good choice. 
  • For this transactional it will be stored 3 years of data and it will be uploaded incrementally, means each month will be uploaded a delta. 

 

Main concerns are:

  • What should be the key for the line items? Concatenation of more than 10 attributes or a sequential number (taking into account that import is done based on deltas)? 
  • It should be the time a dimension or line item in the module?

Thanks for your support. 

 

 

Tagged:

Comments

  • joseantonio.galindo
    joseantonio.galindo Member, ALL USERS, Community Member, Certified Model Builder Posts: 5 Contributor

    Thanks @Anilkumarch 

     

    the point of use stagging list is that the combination of properties will be more than 10 properties, this transactional data has many granularity required by the business to be imported in Anaplan. 

     

    Best regards

  • kmoss
    kmoss Member, ALL USERS, Certified Model Builder Posts: 3 New Contributor

    Hi @rob_marshall 

    I am in a similar system as the original poster, but when I concatenate the codes for each of my 10 attributes from the source system, it exceeds 60 characters.  Is there any best practice way to handle that?

    Thanks.

  • kmoss
    kmoss Member, ALL USERS, Certified Model Builder Posts: 3 New Contributor

    Yes, they are all "codes" but the problem is that the source system was designed where the code value for many of the attributes are effectively the names of the items.  One example "code" is BUSINESS_ACTIVITY_FACILITIES_ELECTRICAL which is 39 characters just in itself and that is only one of the 10 attributes which are being concatenated.

  • kmoss
    kmoss Member, ALL USERS, Certified Model Builder Posts: 3 New Contributor

    Unfortunately, this is not something I can do in the source system.  Is there any alternative best practice for this situation?

Categories