基于.NET Connector 3：能否从IDOCTYPE_READ_COMPLETE获取IDOC结构转RfcStructureMetadata？

Great question! Yes, you absolutely can use the IDOCTYPE_READ_COMPLETE function to retrieve the full IDOC structure metadata, then parse it into RfcStructureMetadata objects. This will let you dynamically build valid segment structures and generate the properly formatted SDATA strings required for IDOC_INBOUND_ASYNCHRONOUS.

Here's a step-by-step breakdown with C# code examples (using SAP .NET Connector 3.0):

1. Call IDOCTYPE_READ_COMPLETE to Fetch Metadata #

First, invoke the function to get the full structure of your target IDOC type. You'll need to specify the IDOC type and optionally its version/extension type.

using SAP.Middleware.Connector;

// Assume you already have an initialized RfcDestination (your SAP connection)
using (var rfcFunction = destination.CreateFunction("IDOCTYPE_READ_COMPLETE"))
{
    // Set required parameters
    rfcFunction.SetValue("IDOCTYPE", "YOUR_IDOC_TYPE"); // e.g., ORDERS05
    rfcFunction.SetValue("CIMTYPE", "3"); // 3 = Extended IDOC type, 1 = Basic type (adjust as needed)
    rfcFunction.SetValue("RELEASE", "750"); // Optional: Target SAP release version

    // Execute the function call
    rfcFunction.Invoke(destination);

    // Extract the DOCSTRUCTURE table, which contains all segment/field details
    var docStructureTable = rfcFunction.GetTable("DOCSTRUCTURE");
}

2. Parse Metadata into RfcStructureMetadata #

The DOCSTRUCTURE table returns each field's details (name, data type, length, offset, etc.). We'll group these by segment name to build RfcStructureMetadata for each segment in your IDOC.

var segmentMetadataMap = new Dictionary<string, RfcStructureMetadata>();

foreach (IRfcTableRow row in docStructureTable)
{
    string segmentName = row.GetString("SEGMENT");
    string fieldName = row.GetString("FIELDNAME");
    string sapDataType = row.GetString("INTTYPE");
    int fieldLength = row.GetInt("LENG");
    int decimalPlaces = row.GetInt("DECIMALS");
    int fieldOffset = row.GetInt("OFFSET");

    // Initialize metadata for the segment if it doesn't exist
    if (!segmentMetadataMap.ContainsKey(segmentName))
    {
        var fieldMetadataList = new List<RfcFieldMetadata>();
        segmentMetadataMap[segmentName] = new RfcStructureMetadata(segmentName, fieldMetadataList);
    }

    // Create field metadata and add to the segment
    var fieldMetadata = new RfcFieldMetadata(
        fieldName,
        RfcDataType.GetDataType(sapDataType),
        fieldLength,
        decimalPlaces,
        fieldOffset,
        RfcFieldDirection.Both
    );

    segmentMetadataMap[segmentName].Fields.Add(fieldMetadata);
}

3. Generate Valid SDATA for IDOC_DATA_REC_40 #

With the RfcStructureMetadata in hand, you can dynamically create segment structures, populate data, and convert them into the fixed-length SDATA string required by the IDOC function module.

// Example: Build and populate the E1EDK01 segment (header segment for ORDERS05)
var e1edk01Metadata = segmentMetadataMap["E1EDK01"];
var e1edk01Segment = new RfcStructure(e1edk01Metadata);

// Populate fields (use correct data types and lengths)
e1edk01Segment.SetValue("BSART", "OR"); // Order type
e1edk01Segment.SetValue("BELNR", "1234567890"); // Document number (padded to field length if needed)
e1edk01Segment.SetValue("BUKRS", "1000"); // Company code

// Convert the structure to the fixed-length SDATA string
// Note: RfcStructure.ToString() will handle padding with spaces for character fields
string sdata = e1edk01Segment.ToString();

// Now you can add this SDATA to an IDOC_DATA_REC_40 row
var idocDataRow = idocDataTable.GetNewRow();
idocDataRow.SetValue("SEGNAM", "E1EDK01");
idocDataRow.SetValue("SDATA", sdata);
idocDataTable.Insert(idocDataRow);

Key Notes #

• Permissions: Ensure your SAP user has authorization to execute IDOCTYPE_READ_COMPLETE (check object S_IDOC_META with activity 03).
• SDATA Format: SDATA is a fixed-length string—always respect the field lengths from the metadata. Character fields must be padded with spaces, numeric fields with leading zeros (depending on SAP's data type rules).
• Nested Segments: For hierarchical IDOCs, use the PARENT field in DOCSTRUCTURE to map child segments to their parent segments, then build nested structures accordingly.
• Version Compatibility: If your IDOC has multiple versions, use the RELEASE parameter in IDOCTYPE_READ_COMPLETE to fetch metadata matching your target SAP system's release.

内容的提问来源于stack exchange，提问作者Miroslav Mikus