TM Forum Community

Hi All,

@Jonathan Goldberg 

Please suggest, should I extend TMF654-PrepayBalance(AdjustBalance) service with below changes? I need to capture tax information with actual total amount information so I am looking for changes.

Option1 : Under amount object

"amount" : {
amount
units
@baseType
@schemaLocation)
@type
"taxAmount" :[{
amount    number($float)
units   string
@baseType    string
@schemaLocation    string($uri)
@type    string
}]
}

Option2 : separate tax amount object

"taxAmount" :[{
amount    number($float)
units   string
@baseType    string
@schemaLocation    string($uri)
@type    string
}]

Hi @Chetan Hirpara 

Have you considered using the ImpactedBucketItem sub-resource to capture the breakdown between amount and tax?

The name field can be used to identify the item as a tax amount.

Hope this helps,

Phil

Hi All,

@Jonathan Goldberg 

Please suggest, should I extend TMF654-PrepayBalance(AdjustBalance) service with below changes? I need to capture tax information with actual total amount information so I am looking for changes.

Option1 : Under amount object

"amount" : {
amount
units
@baseType
@schemaLocation)
@type
"taxAmount" :[{
amount    number($float)
units   string
@baseType    string
@schemaLocation    string($uri)
@type    string
}]
}

Option2 : separate tax amount object

"taxAmount" :[{
amount    number($float)
units   string
@baseType    string
@schemaLocation    string($uri)
@type    string
}]

Hi Phil,

Thanks a lot for response.

Are you suggesting below section to capture amount & tax information ?

Hi @Chetan Hirpara 

Have you considered using the ImpactedBucketItem sub-resource to capture the breakdown between amount and tax?

The name field can be used to identify the item as a tax amount.

Hope this helps,

Phil

Hi All,

@Jonathan Goldberg 

Please suggest, should I extend TMF654-PrepayBalance(AdjustBalance) service with below changes? I need to capture tax information with actual total amount information so I am looking for changes.

Option1 : Under amount object

"amount" : {
amount
units
@baseType
@schemaLocation)
@type
"taxAmount" :[{
amount    number($float)
units   string
@baseType    string
@schemaLocation    string($uri)
@type    string
}]
}

Option2 : separate tax amount object

"taxAmount" :[{
amount    number($float)
units   string
@baseType    string
@schemaLocation    string($uri)
@type    string
}]

Hi Chetan,

I was looking at impactedBucketItem as a sub-resource of impactedBucket. It's included in the spec but I now see it's not included in the Swagger file. One of my colleagues is working on some updates to this API and so I'll see if I can get an answer on whether it's the Spec or Swagger which is wrong.

Thanks,

Phil

Hi Phil,

Thanks a lot for response.

Are you suggesting below section to capture amount & tax information ?

Hi @Chetan Hirpara 

Have you considered using the ImpactedBucketItem sub-resource to capture the breakdown between amount and tax?

The name field can be used to identify the item as a tax amount.

Hope this helps,

Phil

Hi All,

@Jonathan Goldberg 

Please suggest, should I extend TMF654-PrepayBalance(AdjustBalance) service with below changes? I need to capture tax information with actual total amount information so I am looking for changes.

Option1 : Under amount object

"amount" : {
amount
units
@baseType
@schemaLocation)
@type
"taxAmount" :[{
amount    number($float)
units   string
@baseType    string
@schemaLocation    string($uri)
@type    string
}]
}

Option2 : separate tax amount object

"taxAmount" :[{
amount    number($float)
units   string
@baseType    string
@schemaLocation    string($uri)
@type    string
}]

Hi Chetan,

The resources I referred to have been fixed in the latest version of the Swagger which is on its way through the review and approval process.

I attach a copy as a text file here for your reference. Bear in mind that the final published version may differ from this one once all reviews and approvals are complete.

Hope this helps

Phil

Hi Chetan,

I was looking at impactedBucketItem as a sub-resource of impactedBucket. It's included in the spec but I now see it's not included in the Swagger file. One of my colleagues is working on some updates to this API and so I'll see if I can get an answer on whether it's the Spec or Swagger which is wrong.

Thanks,

Phil

Hi Phil,

Thanks a lot for response.

Are you suggesting below section to capture amount & tax information ?

Hi @Chetan Hirpara 

Have you considered using the ImpactedBucketItem sub-resource to capture the breakdown between amount and tax?

The name field can be used to identify the item as a tax amount.

Hope this helps,

Phil

Hi All,

@Jonathan Goldberg 

Please suggest, should I extend TMF654-PrepayBalance(AdjustBalance) service with below changes? I need to capture tax information with actual total amount information so I am looking for changes.

Option1 : Under amount object

"amount" : {
amount
units
@baseType
@schemaLocation)
@type
"taxAmount" :[{
amount    number($float)
units   string
@baseType    string
@schemaLocation    string($uri)
@type    string
}]
}

Option2 : separate tax amount object

"taxAmount" :[{
amount    number($float)
units   string
@baseType    string
@schemaLocation    string($uri)
@type    string
}]

Thanks Phil for helping out here.

Chetan, I recommend that you use the TaxItem entity, you'll find it referenced in the swaggers for TMF678 Customer Bill and TMF620 Product Catalog.

And keep it separate from the basic amount.

Hi Chetan,

The resources I referred to have been fixed in the latest version of the Swagger which is on its way through the review and approval process.

I attach a copy as a text file here for your reference. Bear in mind that the final published version may differ from this one once all reviews and approvals are complete.

Hope this helps

Phil

Hi Chetan,

I was looking at impactedBucketItem as a sub-resource of impactedBucket. It's included in the spec but I now see it's not included in the Swagger file. One of my colleagues is working on some updates to this API and so I'll see if I can get an answer on whether it's the Spec or Swagger which is wrong.

Thanks,

Phil

Hi Phil,

Thanks a lot for response.

Are you suggesting below section to capture amount & tax information ?

Hi @Chetan Hirpara 

Have you considered using the ImpactedBucketItem sub-resource to capture the breakdown between amount and tax?

The name field can be used to identify the item as a tax amount.

Hope this helps,

Phil

Hi All,

@Jonathan Goldberg 

Please suggest, should I extend TMF654-PrepayBalance(AdjustBalance) service with below changes? I need to capture tax information with actual total amount information so I am looking for changes.

Option1 : Under amount object

"amount" : {
amount
units
@baseType
@schemaLocation)
@type
"taxAmount" :[{
amount    number($float)
units   string
@baseType    string
@schemaLocation    string($uri)
@type    string
}]
}

Option2 : separate tax amount object

"taxAmount" :[{
amount    number($float)
units   string
@baseType    string
@schemaLocation    string($uri)
@type    string
}]

Hi Chetan,

The resources I referred to have been fixed in the latest version of the Swagger which is on its way through the review and approval process.

I attach a copy as a text file here for your reference. Bear in mind that the final published version may differ from this one once all reviews and approvals are complete.

Hope this helps

Phil

Hi Chetan,

I was looking at impactedBucketItem as a sub-resource of impactedBucket. It's included in the spec but I now see it's not included in the Swagger file. One of my colleagues is working on some updates to this API and so I'll see if I can get an answer on whether it's the Spec or Swagger which is wrong.

Thanks,

Phil

Hi Phil,

Thanks a lot for response.

Are you suggesting below section to capture amount & tax information ?

Hi @Chetan Hirpara 

Have you considered using the ImpactedBucketItem sub-resource to capture the breakdown between amount and tax?

The name field can be used to identify the item as a tax amount.

Hope this helps,

Phil

Hi All,

@Jonathan Goldberg 

Please suggest, should I extend TMF654-PrepayBalance(AdjustBalance) service with below changes? I need to capture tax information with actual total amount information so I am looking for changes.

Option1 : Under amount object

"amount" : {
amount
units
@baseType
@schemaLocation)
@type
"taxAmount" :[{
amount    number($float)
units   string
@baseType    string
@schemaLocation    string($uri)
@type    string
}]
}

Option2 : separate tax amount object

"taxAmount" :[{
amount    number($float)
units   string
@baseType    string
@schemaLocation    string($uri)
@type    string
}]

Hi Chetan,

The resources I referred to have been fixed in the latest version of the Swagger which is on its way through the review and approval process.

I attach a copy as a text file here for your reference. Bear in mind that the final published version may differ from this one once all reviews and approvals are complete.

Hope this helps

Phil

------------------------------
Phil Moss
MATRIXX Software

Original Message:
Sent: Jun 13, 2023 05:18
From: Phil Moss
Subject: TMF654-PrepayBalance Extension

Hi Chetan,

I was looking at impactedBucketItem as a sub-resource of impactedBucket. It's included in the spec but I now see it's not included in the Swagger file. One of my colleagues is working on some updates to this API and so I'll see if I can get an answer on whether it's the Spec or Swagger which is wrong.

Thanks,

Phil

Hi Phil,

Thanks a lot for response.

Are you suggesting below section to capture amount & tax information ?

------------------------------
Chetan Patel
Tech Mahindra Limited

Original Message:
Sent: Jun 13, 2023 04:45
From: Phil Moss
Subject: TMF654-PrepayBalance Extension

Hi @Chetan Hirpara 

Have you considered using the ImpactedBucketItem sub-resource to capture the breakdown between amount and tax?

The name field can be used to identify the item as a tax amount.

Hope this helps,

Phil

Hi All,

@Jonathan Goldberg 

Please suggest, should I extend TMF654-PrepayBalance(AdjustBalance) service with below changes? I need to capture tax information with actual total amount information so I am looking for changes.

Option1 : Under amount object

"amount" : {
amount
units
@baseType
@schemaLocation)
@type
"taxAmount" :[{
amount    number($float)
units   string
@baseType    string
@schemaLocation    string($uri)
@type    string
}]
}

Option2 : separate tax amount object

"taxAmount" :[{
amount    number($float)
units   string
@baseType    string
@schemaLocation    string($uri)
@type    string
}]

Ist this version (4.1.0) of the api supposed to be published on https://www.tmforum.org/oda/open-apis/table ? 

Hi Chetan,

The resources I referred to have been fixed in the latest version of the Swagger which is on its way through the review and approval process.

I attach a copy as a text file here for your reference. Bear in mind that the final published version may differ from this one once all reviews and approvals are complete.

Hope this helps

Phil

Hi Chetan,

I was looking at impactedBucketItem as a sub-resource of impactedBucket. It's included in the spec but I now see it's not included in the Swagger file. One of my colleagues is working on some updates to this API and so I'll see if I can get an answer on whether it's the Spec or Swagger which is wrong.

Thanks,

Phil

Hi Phil,

Thanks a lot for response.

Are you suggesting below section to capture amount & tax information ?

Hi @Chetan Hirpara 

Have you considered using the ImpactedBucketItem sub-resource to capture the breakdown between amount and tax?

The name field can be used to identify the item as a tax amount.

Hope this helps,

Phil

Hi All,

@Jonathan Goldberg 

Please suggest, should I extend TMF654-PrepayBalance(AdjustBalance) service with below changes? I need to capture tax information with actual total amount information so I am looking for changes.

Option1 : Under amount object

"amount" : {
amount
units
@baseType
@schemaLocation)
@type
"taxAmount" :[{
amount    number($float)
units   string
@baseType    string
@schemaLocation    string($uri)
@type    string
}]
}

Option2 : separate tax amount object

"taxAmount" :[{
amount    number($float)
units   string
@baseType    string
@schemaLocation    string($uri)
@type    string
}]