Skip to content

Commit 1d2eb26

Browse files
LLC-23
1 parent 376e8ee commit 1d2eb26

File tree

3 files changed

+14
-5
lines changed

3 files changed

+14
-5
lines changed

rules/snippets/application-response/snippet-1.xml

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,9 @@
1212
<cbc:IssueTime>12:00:00</cbc:IssueTime>
1313
<cac:SenderParty>
1414
<cbc:EndpointID schemeID="0088">5798000012349</cbc:EndpointID>
15+
<cac:PartyName>
16+
<cbc:Name>Sender</cbc:Name>
17+
</cac:PartyName>
1518
<cac:PartyLegalEntity>
1619
<cbc:RegistrationName>Buyer organization</cbc:RegistrationName>
1720
</cac:PartyLegalEntity>
@@ -23,6 +26,9 @@
2326
</cac:SenderParty>
2427
<cac:ReceiverParty>
2528
<cbc:EndpointID schemeID="0088">7330001000000</cbc:EndpointID>
29+
<cac:PartyName>
30+
<cbc:Name>Receiver</cbc:Name>
31+
</cac:PartyName>
2632
<cac:PartyLegalEntity>
2733
<cbc:RegistrationName>Seller company</cbc:RegistrationName>
2834
</cac:PartyLegalEntity>

structure/source/how_to_add_a_document.txt

Lines changed: 7 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,15 @@
1-
This documentation guids you through the simple steps to add a new document to the Peppol documentation generation tool
1+
This documentation guides you through the simple steps to add a new document (BIS and/or transaction) to the Peppol documentation generation tool
22

3-
Step 1. Add the exampel file to the /structure/source/ directory.
3+
Step 1a. Add the exampel file to the /structure/source/ directory.
44
Make sure that the DocumentTerm and properties processing instruction are included
55
e.g.
66
<?DocumentTerm DespatchAdvice?>
77
<?Property key="sch:prefix" PEPPOL-T16?>
88
<?Property key="sch:identifier" T16-basic?>
99

10+
Step 1b. Add the folders and documents that are the base of the BIS to the /guides/profiles directory. Normally something existing is copied and given
11+
a suitable name.
12+
1013
Step 2. Create namespace document in the /structure/namespace directory if there is no existing namespace document for the transaction
1114

1215
Step 3. Add files to /rules/sch/ and the /rules/sch/parts directories copy a simple file e.g. PEPPOLBIS-T122.sch and PEPPOL-M-T122.sch
@@ -19,11 +22,11 @@ Edit the files to the corresponding
1922
Step 4. Edit /rules/buildconfig.xml
2023
Step 4a. Add unit test folder e.g.
2124
<testfolder>unit-advanced-despatch-advice</testfolder>
22-
And create the folder for others to add the unit tests
25+
And create the folder for others to add the unit tests. You also need to create a file with the normal naming standard in the new folder.
2326

2427
Step 4b. Add snippet folder e.g.
2528
<testfolder>snippets/advanceddespatch</testfolder>
26-
And create the folder for others to add snippets
29+
And create the folder for others to add snippets. You also need to create a file with the normal naming standard in the new folder.
2730

2831
Step 4c. Add base configuration for the transaction e.g.
2932
<configuration>

structure/source/ubl-application-response.xml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@
66
<?Property key="sch:prefix" PEPPOL-T129?>
77
<?Property key="sch:identifier" T129-basic?>
88
<cbc:CustomizationID>urn:fdc:peppol.eu:logistics:trns:application_response:1</cbc:CustomizationID>
9-
<cbc:ProfileID>urn:fdc:peppol.eu:logistics:bis:transport_execution_plan_request_response_and_dialog:1</cbc:ProfileID>
9+
<cbc:ProfileID>urn:fdc:peppol.eu:logistics:bis:advanced_transport_execution_plan:1</cbc:ProfileID>
1010

1111
<cbc:ProfileExecutionID>XZ-4532
1212
<?Name Profile Execution ID?>

0 commit comments

Comments
 (0)