1. ALLIANCE Administration 20 Oct 2009 (Based on Release 2.2) Michaël Petit

2. Summary I Requests administration 1)Web services call 2)SQL queries execution II B2B message administration 1)Message file managment 2)Message status managment III B2B flows administration 1)Flow determination 2)Flow parameters IV Operands and checker administration 1)Checker general rules management 2)Operands & operators rights management 3)Operands and operators list V CCC administration 1)CCC managment VI Environment information 1)Environment info 2)Event log viewer

3. I Requests administration

4. I Requests administration 1) Web services Used to call manually some very useful Alliance webservices involved mostly in the B2B-Order processes. Except for reload data and Message validation, all webservices need a dedicated xml file to proceed. Once data are sent to webservice, a return code and description is displayed.  0 : Data correctly treated  Other : Related to triggered error (see return description) Available webservices Upload xml file area Return code Return description Response if needed

5. I Requests administration 1) Web services ReloadData : Allow the refresh of a part of Alliance singleton and cache data. Different than the administration “reload data” button. Must be used in case of B2B flow update. PlaceHandoverDate : Allow simulation of BP to Customer information regarding delivery date given by the supply chain. PlaceInvoiceTrigger : Allow simulation of customer to Alliance information regarding billing acknowledgement. OutgoingMessageValidation : Allow simulation of customer to Alliance information regarding POR acknowledgement. PlacePurchaseOrderRequest : Allow B2B message creation (New PO, PO change full & delta) PlacePurchaseOrderResponse : Allow B2B message response creation (Manual) PlaceBackOfficeCFF : Allow simulation of BP return after order sent LoadAcrData : Allow Customer data loading in Alliance LoadAprData : Allow Alcatel Product data loading in Alliance LoadCustomerCatalog : Allow CCC Idoc file data loading in Alliance

6. I Requests administration 2) SQL queries excecution Used to excecute read only sql queries on Alliance Data Base.

7. II B2B message administration

8. II B2B message administration 1) Message managment Used to delete, change some flags or download files regarding loaded B2B message. Delete B2B message not transfered in order Download the xml file of the defined message ID Lock the defined message with specific user Release the locked defined message Remove the flag from a duplicated conversation where one message remains. Excecute checker over defined message Download templates

9. II B2B message administration 2) Message status managment Used to change manually the checker/Transfer status, B2B gateway ID and related Business Unit of a specified message.

10. III Flows administration

11. III Flows administration 1) Flow determination Used to manage the first step of B2B message entry : Bu identification, based on customer + legal unit or Customer + legal unit + one extra data (most of the time a catalog (Frame Agreement) data. As Customer and Legal unit (Selling unit) are given in the B2B message, this screen helps to find which Business unit will be involved in message managment.

12. III Flows administration 1) Flow determination In some cases, there is only one legal unit dedicated to a customer but multiple business unit are involved, that means that customer and legal unit could be the same for different line. A condition (present in the B2B message) is used to determine the correct business unit  Condition could be whatever xml tag data. There are two ways of flow determination creation :  Simple addition : Choose A customer, a legal unit and the related business unit and click on “Add”

13. III Flows administration 1) Flow determination  Addition with condition : Choose A customer, a legal unit and the related business unit and click on “Add (with condition)” then edit the flow determination : 1 : Create a line without condition 2 : Edit the line 3 : Choose one condition data 4 : Edit the condition data 5 : Enter a value for this condition 6 : Save the condition value 7 : Save Flow edition

14. III Flows administration 2) Flow parameters Used to manage the second step of B2B message entry : Flow identification and excecution of the defined parameters on the related message. A flow is identified by a couple Customer + Business unit. A flow is mandatory to manage B2B message. If no Business unit exists, a default one will be used in order to create one flow. Delete one flow Edit one flow Edit the flow’s PO response data Copy the flow settings to the upper one

15. III Flows administration 2) Flow parameters Flow edition allows to manage the B2B message parameters used in checker enrichment and response processes. Message authorized behavior (view, check, transfer) Message enrichement type Checker activation CO structuring activation / Exctract logisticals activation Email notification activation Delay before automatic archiving of processed messages Delay before automatic archiving of inprocess messages Maximum number of PO response allowed per message Default CCC ID used for all messages linked to this flow Automatic transfer to order in case of neither warnings nor error during checker

16. IV Operands and checker administration

17. IV Operands and checker administration 1) Checker general rules managment Used to manage the checker non editable rules. Create, edit, delete and copy as dedicated CCC rule to a specific CCC.

18. IV Operands and checker administration 2) Operands & operators right managment Operands use can be limited to specific rights based on customer and business unit. To manage such rights, go to administration “Operands & operator management”

19. IV Operands and checker administration 3) Operands & operators list Operands can be visualized through the administration screen “Operands end operator list”

20. V CCC administration

21. V CCC administration 1) CCC managment Used to manage the loaded or loading CCC. Allow to delete a loaded and non linked CCC Allow to clean values from temporary CCC table Get the xls or csv file from the temporary table Allow to see and delete CCC files in FTP folders used during CCC upload process

22. VI Environment information

23. VI Environment information 1) Environment info Displays all configuration data used in Alliance :  Webconfig data  Urls (FTP, file system…)  Winform info  …

24. VI Environment information 1) Event log Major part of application error and information logs are stored in this area.  Uncatched errors  Enrichment errors  … Load application log Go to specified log page