Structure of SaveXML invoice data

Question

I do not understand the structure of the invoice XML schema.  I created a file, invoice.xml, using  BoObjectTypes.oInvoices, GetByKey method, and SaveXML method in my C# project.  I created this file based on one invoice in the SAP demo database (Invoice # 10). The structure of the XML appears to contain 3 invoices, OINV, INV1, and INV3, all referencing the invoice number in the DocEntry field.  INV1 contains the detail data, but it is not enveloped inside of the OINV tags. INV3 contains tax information, but it also is not enveloped inside OINV.  I am trying to map this information to an EDI document.  Is there a different invoice schema that I can use with the Header tags surrounding all of the detail or line item tags?  Below is part of the data from my xml file.
Thanks,
Nancy
[email protected]  
<?xml version="1.0" encoding="UTF-16" ?>
- <BOM>
- <BO>
- <AdmInfo>
  <Object>13</Object>
  </AdmInfo>
- <OINV>
- <row>
  <DocEntry>10</DocEntry>
  <DocNum>10</DocNum>
  <DocType>I</DocType>
  <CANCELED>N</CANCELED>
  <Handwrtten>N</Handwrtten>
  <Printed>N</Printed>
</row>
  </OINV>
- <INV1>
- <row>
  <DocEntry>10</DocEntry>
  <LineNum>0</LineNum>
  <TargetType>0</TargetType>
  <TrgetEntry>0</TrgetEntry>
  <BaseRef />
  <BaseType>-1</BaseType>
  <BaseEntry>0</BaseEntry>
  <BaseLine>0</BaseLine>
  <LineStatus>O</LineStatus>
</row>
  </INV1>
  <OSRI />
  <OIBT />
  <INV2 />
  <INV5V />
- <INV3>
- <row>
  <DocEntry>10</DocEntry>
  <ExpnsCode>2</ExpnsCode>
  <LineTotal>5.000000</LineTotal>
  <TotalFrgn>0.000000</TotalFrgn>
  <TotalSumSy>5.000000</TotalSumSy>
  <PaidToDate>0.000000</PaidToDate>
  <PaidFC>0.000000</PaidFC>
</row>
  </INV3>
  <INV5 />
  <INV12 />
  </BO>
  </BOM>

Answer 1

Don't have B1 on this machine just now so the following is from memory.  Might not be 100% accurate but should give you a good start:-
To understand the XML schema it is first important to consider the database structure and the existing DI API object structure.  "ONIV" contains the invoice header, associated with this there can be multiple lines "INV1", and also other associated files (eg INV2, INV3 etc).  The XML schema uses this same structuring.
The <BO> element encapsulates the entire invoice object - header and all line details for a single invoice.  I think this stands for "Business Object" and can include anything such as an invoice, order etc.
The first section in the <BO> object is the <AdmInfo> - this tells you what type of "Business Object" it is.  In this case it is type=13 which is an invoice.
As it is type=13, you can then expect to see <OINV>, <INV1>, <INV2> etc elements which will contain the actual data.  If it had been for example type=17, then this would have represented a sales order and you would get <ORDR>, <RDR1>, <RDR2> etc elements instead of the <OINV> ones.
If you had 3 invoices in the file you would see 3 <BO> elements, each of them would have their own <INV1>, <INV2> etc. elements inside them.
The schemas themselves can be generated for reference purposes out of the DI-API itself.  I can't recall the exact method name and I don't have B1 on this machine just now.  If you search in the DI help file for "schema" you probably find it.  Examining the schemas should also help to clarify their structure.
Hope this helps,
John