{"text_format":"1","workbook":"xlsx","n_sheets":3,"sheets":["Classifications","ServerList","Instructions"],"not_rendered":{"charts":0,"images":0,"macros":1,"external_links":0,"defined_names":2,"comments":0,"pivot_tables":0},"unopened":[],"bounds":{"document_bytes":16777216,"sheet_cells":100000,"rows_first":2000,"rows_last":500,"rows_between":2000,"halvings":0,"cell_chars":16384,"cell_head_chars":4096},"cells_cut":0,"cells_raw":0,"read":"whole","date_system":"1900"}

{"sheet":"Classifications","index":0,"n_rows":1,"n_cols":6,"rows_kept":1,"cut":false,"hidden":false,"merged":[]}
["Q01","OBJEK","KLART","CLASS","ATNAM","ATWRT"]

{"sheet":"ServerList","index":1,"n_rows":4,"n_cols":10,"rows_kept":4,"cut":false,"hidden":false,"merged":[]}
["SAP System","System Number","Client","Application Server",null,null,null,"Object Table:","MARA","<-- Put the Object Table like KNA1 or MARA. You can track down the correct table by finding it in the INOB and TCLO tables."]
["D01","00","100","d01server.company.int"]
["Q01","00","100","q01server.company.int"]
["P01","00","100","p01server.company.int"]

{"sheet":"Instructions","index":2,"n_rows":4,"n_cols":1,"rows_kept":4,"cut":false,"hidden":false,"merged":[]}
["Getting Started: \n\nAdd the SAP servers to which this tool will connect in the ServerList tab.  Include the System, SystemNumber, Client and ApplicationServer values.  These servers are then available in the dropdown menu located in Cell A1 of the Classifications tab.\n\nChange the Object Table value in field I1 of the ServerList tab to reflect the Object Table associated with the Objects being allocated with Classification data (MARA, KNA1, etc.).  This is used downstream when calling the BAPIs and when teasing out the SAP tables associated with the Classifications and Characteristics.  The Object Table can likely be found in the INOB table with a little effort by searching for existing allocations. \n\nLeaving field I1 blank in the ServerList tab is not allowed; for help connecting an Object to the Object Table, look for its Transaction Code in the TCLO table.  The list of Classification Types is based on the Object Table value.  Narrowing down the number of KLART values to check against Objects will speed up the process, reduce RFC traffic and eliminate confusion and problems where Object number ranges overlap. \n\nWhen extracting and loading data, be sure to select the correct server in Cell A1 of the Classifications tab.  This tells Excel with which server to interact.  To migrate Classification data, extract from the source server and load to the target server."]
["Extract data: \n\nProvide the Object number in the OBJEK column and optionally the Classification Type in the KLART column.  Click the \"Extract\" button.  Where the KLART value is left blank, all of the Classification Types associated with the Object Table on the ServerList tab will be checked.\n\nThe tool loops through the rows where the A column is empty looking for data to extract.  If a value exists in the CLASS column then the extract routine assumes that this row is extracted data and skips it. "]
["Load data:\n\nProvide all the values in the columns B through F and optionally G.  Column G is used for \"VALUE_TO\" when Numeric Characteristics are represented by a range or the Currency when dealing with Currency Characteristics.  When a numeric value is just one number and not a range, the value in Column G can be left blank or set to zero. \n\nWhen loading the data, the tool first extracts the existing Characteristic data (if any) into memory, overwrites the data in memory with the Characteristics provided and then writes all of the combined data back to SAP.  When loading just one Characteristic for many Objects, this ensures that the data in all other Characteristics are not lost, but preserved when just the one Characteristic value is updated. "]
["Notice: Like all tools provided by SAPLSMW.com, this tool comes with no warranty, implied or expressed.  SAPLSMW.com is not liable for any damage or data loss.  Be sure to test this tool thouroughly in a sandbox to ensure that it functions as expected before using it in a production SAP system. "]