Minghui SAP Data Query

Problem

Inside Minghui Group, SAP queries often break on small details rather than access itself: material barcodes missing leading zeros, production order numbers with the wrong length, dates not in YYYYMMDD, and table queries lacking consistent pagination, field limits, and error formats. sap connect targets these recurring details and puts WeCom authentication, BAPI calls, table/view queries, and result export under one shared convention.

How It Works

The skill follows a fixed path: WeCom authentication first obtains a 24-hour Ticket, then selects BAPI calls or table/view queries based on intent. Before execution, it normalizes parameters, for example left-padding material barcodes to 18 characters and production order numbers to 12 characters, and converts dates such as 2024-04-22 to 20240422. Queries support field selection, filters, pagination, timeout, and data-volume controls, then produce standardized output that can be exported as JSON, Excel, or CSV.

Boundaries

This skill is restricted to the Minghui Group internal network and depends on IP allowlists, rate limits, and internal authentication. Typical limits include 10,000 rows per page, 100 pages, 50 returned fields, and a 60-second timeout. For large result sets, narrow filters and reduce fields first. The last six digits of the ID number are used only for authentication, sensitive data is masked, and query logs are stored encrypted according to internal requirements.