马上开始. 它是免费的哦
注册 使用您的电邮地址
Sales Systems 作者: Mind Map: Sales Systems

1. Aimee.Marketing.API

1.1. Jobs to ReportingDB

1.1.1. (Core Marketing) Save Marketing Reports

2. Aimee.FinancialEngine.API

2.1. Jobs

2.1.1. (Core Sales) Download EU Reports to Blob

2.1.2. (Core Sales) Download FBA Returns

2.1.3. (Core Sales) Download FBM Returns

2.1.4. (Core Sales) Download FinancialReports (per Account)

2.1.4.1. Trigger FinancialEngine AmazonFees per Account job afterwards

2.1.5. (Core Sales) Synchronize core schemas with skus

2.2. APIs

2.2.1. (Core Sales) Reprice/Price Change (Proxy Endpoint to Supply) - depreacted

2.2.1.1. Or can this be directly done in Strategy?

2.2.1.2. Probably doesn't know any connection to supply?

2.2.2. (Core Sales) Brand server webhook to receive performance reports

2.2.2.1. Consolidate FinancialEngine Webhook endpoint to process directly the brand server webhook response

2.2.3. (Core Sales) [POST] Strategy Logs send by Strategy Engine

2.2.3.1. Get rid in strategy to post to azure queue

2.2.4. SKUs for Master SKU endpoint

2.2.4.1. Endpoint is backed with Financial Engine data

2.2.4.2. Strategy engine uses this endpoint. We can maybe update Strategy Engine to hit Financial Engine directly instead

2.2.4.3. Can we re-use an existing endpoint in FinancialEngine and connect strategy engine to it?

2.2.5. Sales endpoints

2.2.5.1. Strategy engine uses this endpoint but also uses some Financial Engine sales endpoints. Strategy engine needs to be refactored to ONLY use financial engine

2.2.5.2. Can we re-use an existing endpoint in FinancialEngine and connect strategy engine to it?

2.2.6. Strategy Log endpoint

2.2.6.1. Question is where is this log data (which schema) and should be likely migrated into financialengine schema then

3. Aimee.FinancialEngine.Maintenance.API

3.1. Jobs to ReportingDB

3.1.1. (Core Sales) Save SKU Strategy Logs

3.1.1.1. Should not be stored in core schema?

3.1.1.2. Is this really to the reporting db? why are the logs (and below) needed there? (eric)

3.1.2. (Core Sales) Save Strategy Output Logs

3.1.2.1. Reads strategy output logs from blob storage (populated by Strategy Engine)