Documentation format
There's a very interesting list in
http://otn.oracle.com/oramag/webcolumns/2003/techarticles/burleson_cbo_pt2_l1.html, but its format isn't nice.
Could you please help me ?
Thanks for bringing this to our attention...this will be fixed in a few hours.
Similar Messages
-
Technical Documentation Format
Hello,
Any body have Technical documentation format. I got the requirements
I have to convert the req into technical documentation.
Regards,
Alexanswered
-
Hi.
I'm looking for SAPu2019s documentation format, somebody knows where it found ? I want to use it like a guide to create a internal format that we can use to reflect system changes.
I will appreciate your help.
Regards,
Manuel H.Hi Russell,
I find my ways into the help always trying to narrow down a bit my search criteria.
For instance:
If I know that I want something that it's from the basis NetWeaver, I select to only search from a release of NetWeaver of my choice. Let me give you a good example:
A few days ago I was searching for documentation of Web Dispatcher with SSL. Without selecting specifically to search results for NetWeaver, I've received TONS of documentation of other applications who suggested to use Web Dispatcher, but not the documentation of the Web Dispatcher itself.
It's preety effective to narrow down the product that you are searching for. It helped me a lot.
Cheers,
Maurício -
*EPUB or *MOBI documentation format?
Some while ago I have seen some Nexus 7000 documentation provided for download also in a *epub format (not only *pdf) on the cisco website.
Example:
http://www.cisco.com/en/US/partner/docs/switches/datacenter/sw/5_x/nx-os/upgrade/guide/b_Cisco_Nexus_7000_Series_NX-OS_Software_Upgrade_and_Downgrade_Guide__Release_5.x.html
Is there a plan to provide all the new documentation (also for other products) maybe also some subset of the older documentation in *epub format?
Thanks.
MarekHi Marek,
Thanks for your question about EPUBs. Yes, we're planning to make more documents available in EPUB (and eventually also MOBI) format.
Thanks,
Michele Greenfield -
BW project documentation format
Hi,
Can anyone send me a format for BW project documentation. my email id is :
[email protected]
Thanks in advance..Hi,
Following document is the sample BI PROJECT BLUEPRINT Documentation realted to
FI Module.
BI Project
ASAP Business Blueprint
Accounts Receivable
BI TEAM
ASAP Business Blueprint
FI-Accounts Receivable
Project Mission Excellence
Created by : BI Team
Date of creation : 28.02.2007
Changed by :
Date of the last changes :
Version : BW 3.53 V
Sign Off Date Signature Customer Signature Consultant
BW: Accounts Receivable Analysis
FIAR LINE ITEM (Info Cube)
This enables you to analyze accounts receivable data from SAP R/3.
Info Cubes Used
 Accounts Receivable: Line Items (technical name FI_AR_C03
Key Points
 Analysis of accounts receivable line items
 Analysis of the payment history (payment volume and days in arrears) of customers per company code and fiscal year period
FI_AR_C03
This Info Cube enables you to view information about accounts receivable line items from R/3 such as:
 Dealer wise/Customer wise monthly collection /cheque returns/Net Collection
 Sales officer wise monthly collection
 Branch wise collection
 Net Collection Report.
 Book Debt Summary.
Data flow for Cube 0FIAR_C03 ( FI AR Line Items )
FIAR LINE ITEM (ODS)
1 Scope
Technical Name: FI_AR_C03
This Info Cube contains all the Accounts Receivable line items that will be loaded from the R/3 system.
2 Expectations / Requirements:
All Collection related reports based on different parameters for e.g.: Day, month, Business Area, Posting Date will be built upon this cube.
3 Data Modeling
Characteristics Technical Name Approx. No
Of Records Enhancement Dimension
Company Code 0COMP_CODE Company Code
G/L Account 0GL_ACCOUNT G/L Account
Credit Control Area 0C_CTR_AREA Customer
Special G/L indicator 0SP_GL_IND Document Data
Baseline date for due date calculation 0BLINE_DATE Due Dates
Payment method 0PYMT_METH Payment Data
Payment block key 0PMNT_BLOCK Payment Data
Terms of payment key 0PMNTTRMS Payment Data
Chart of accounts 0CHRT_ACCTS G/L Account
Account type 0ACCT_TYPE G/L Account
Country key 0COUNTRY Payment Data
Customer number 0DEBITOR Customer
Item Status 0FI_DOCSTAT Document Status
Account Number of the Branch 0FI_SUBSID Dunning Data
Posting date in the document 0PSTNG_DATE Document Data
Clearing date 0CLEAR_DATE Payment Data
Document type 0AC_DOC_TYP Document Data
Document Date 0DOC_DATE Document Data
Posting key 0POST_KEY Document Data
Dunning area 0DUNN_AREA Dunning Data
Date of last dunning notice 0LAST_DUNN Dunning Data
Dunning block 0DUNN_BLOCK Dunning Data
Dunning level 0DUNN_LEVEL Dunning Data
Dunning key 0DUNN_KEY Dunning Data
Due date for net payment 0NETDUEDATE Due Dates
Reason code for payments 0REASON_CDE Due Dates
Business Area 0BUS_AREA Enhancement Product
Fiscal year / period 0FISCPER Time
Fiscal year variant 0FISCVARNT Time
Fiscal Year 0FISCYEAR Time
Division 0DIVISION Enhancement Product
Employee 0EMPLOYEE Enhancement Sales Area
Sales Office 0SALES_OFF Enhancement Sales Area
Cycle Wise Week V_CYCWEEK Enhancement Document Data
Dimension Approx. Entries Line Item
Company Code
Customer
Payment Data
Due Dates
G/L Account
Document Data
Sales Area
Dunning Data
Data Sources Involved App. Comp.
0FI_AR_4 FI-AR
0FI_SUBSID_TEXT FI-IO
0GL_ACCOUNT_TEXT FI-IO
0PMNTTRMS_TEXT FI-IO
0PMNT_BLOCK_TEXT FI-IO
0PYMT_METH_TEXT FI-IO
0ACCT_TYPE_ATTR FI-IO
0CHRT_ACCTS_ATTR FI-IO
0COMP_CODE_ATTR FI-IO
0C_CTR_AREA_ATTR FI-AR-IO
0GL_ACCOUNT_ATTR FI-IO
0PMNT_BLOCK_ATTR FI-IO
0PYMT_METH_ATTR FI-IO
0SP_GL_IND_ATTR FI-IO
0ACCT_TYPE_TEXT FI-IO
0AC_DOC_TYP_TEXT FI-IO
0CHRT_ACCTS_TEXT FI-IO
0COMP_CODE_TEXT FI-IO
0COUNTRY_TEXT SAP-R/3-IO
0REASON_CDE_TEXT FI-IO
0SP_GL_IND_TEXT FI-IO
0C_CTR_AREA_TEXT FI-AR-IO
0CUSTOMER_ATTR LO-IO
0CUSTOMER_TEXT LO-IO
Navigation Attributes
0COMPANY Company
0BAL_FLAG Indicator: G/L Account is Balance Sheet Account
0INCST_FLAG Indicator: G/L Account is P&L Account
0SEM_POSIT Planning Item
0BPARTNER Business Partner
0COUNTRY Country key
0INDUSTRY Industry sector
0SALES_OFF__0COUNTRY Country
0SALES_OFF__0REGION Region
0SALES_OFF__0SALES_DIST Sales District
KEY FIGURES
Description Technical Name Unit
Amount in Local Currency with +/- Signs 0DEB_CRE_LC 0LOC_CURRCY
Cash discount amount in local currency 0DSC_AMT_LC 0LOC_CURRCY
Foreign currency amount with signs (+/-) 0DEB_CRE_DC 0DOC_CURRCY
Cash discount amount in document currency 0DSC_AMT_DC 0DOC_CURRCY
Credit amount in foreign currency 0CREDIT_DC 0DOC_CURRCY
Credit amount in local currency 0CREDIT_LC 0LOC_CURRCY
Debit amount in foreign currency 0DEBIT_DC 0DOC_CURRCY
Debit amount in local currency 0DEBIT_LC 0LOC_CURRCY
Cycle Wise Balances V_CYCBAL Currency
4 Data Loading Strategy (Frequency, event chain)
Data will be loaded daily in this cube using suitable process chains.
5 Transfer rules
Standard Business Content Transfer rules will be enhanced with Business Area, Cycle Week and Employee.
6 Update Rules (start routine, return table)
Standard Business Content Update rules will be enhanced with Business Area and Division.
7 Virtual key figures / Characteristics
Not required.
8 Aggregates
If required suitable aggregates will be created after going live according to BW statistics proposals.
9 Enhancements, Gaps and Possible Approaches to Bridge the Gaps
Business Area, Division, Employee and Cycle Week are not present in the standard cube. The cube will be enhanced with the above-mentioned characteristics and to derive the values of the same the exit RSAP0001 will be used to enhance the data source 0FI_AR_4.
Sales Employee: Check return or reversal get original document based on check number and find sales employee for original document.
Cycle Week: derived cycle week from Period. For cycle wise reporting.
Document Type: DU & DZ hard coded for Collection and BB & BE hard coded for Check Return.
Fiscal year variant: Fiscal year Variant W2 is hard coded for Company Cycle.
10 Assumptions / Prerequisites
11 Authorization and User Roles
Company Code, Branch/Sales Office, Division.
FIAR LINE ITEMS ODS
1 Scope
Technical name: 0FI_AR_O03
2 Expectations / Requirements:
3 Data Modeling
List of Objects in the ODS are same as in FIAR Line Items Cube.
Following Objects are taken, as Key Fields and rest all are Data Fields.
1. Company Code
2. Customer Number
3. Fiscal Year
4. Fiscal Year Variant
5. Accounting Document Number
6. Number of Line Item within Accounting Number
7. Due Date Item Number
8. Cycle Week
4 Data Loading Strategy (Frequency, event chain)
Data will be loaded daily to this ODS using suitable process chains.
5 Transfer rules
Standard Business Content Transfer rules will be used.
6 Update Rules (start routine, return table)
Standard Business Content Update rules will be used
7 Virtual key figures / Characteristics
Not required.
8 Aggregates
Not Applicable
9 Enhancements, Gaps and Possible Approaches to Bridge the Gaps
Business Area, Employee and cycle week are not present in the standard ODS. The ODS will be enhanced with the above-mentioned characteristics and to derive the values of the same the exit RSAP0001 will be used to enhance the data source 0FI_AR_3.
10 Assumptions / Prerequisites
11 Authorization and User Roles
FIAR Transaction Data
Data Flow for Cube OFI_AR_C02
1 Scope
Technical name: 0FIAR_C02
This Info Cube contains all accounts receivable data (transaction figures) that was downloaded from the connected source system(s).
2 Expectations / Requirements:
This Cube enables to calculate dealer wise net collection by calculating collection and cheque return. Here you can analyze collection value, cheque return value and net collection value. The net collection value is derived after subtracting cheque return value from the collection value.
3 Data Modeling
CHARACTERISTICS
Characteristic Technical Name Approx No Of Records Enhancement Dimension
Company code 0COMP_CODE Company Code
Currency Type 0CURTYPE Currency Type
Customer number 0DEBITOR Customer
Fiscal year 0FISCYEAR Time
Fiscal year / period 0FISCPER Time
Fiscal year variant 0FISCVARNT Time
Posting period 0FISCPER3 Time
Business Area 0BUS_AREA Enhancement Business Area
Profit Center 0PROFIT_CTR Enhancement Profit Center
Dimension Approx. Entries Line Item
Customer
Company Code
Currency Type
Data Sources Involved App. Comp.
0FI_AR_6 FI-AR
0COMP_CODE_ATTR FI-IO
0COMP_CODE_TEXT FI-IO
0CUSTOMER_ATTR LO-IO
0CUSTOMER_TEXT LO-IO
0PROFIT_CTR_ATTR FI-IO
0PROFIT_CTR_TEXT FI-IO
0BUS_AREA_ATTR EC-PCA-IO
0BUS_AREA_ TEXT EC-PCA-IO
Navigation Attributes
0DEBITOR__0BPARTNER Business Partner
0DEBITOR__0COUNTRY Country key
0DEBITOR__0INDUSTRY Industry sector
0COMP_CODE__0COMPANY Company
KEY FIGURES
Description Technical Name Unit Enhancement
Accumulated balance 0BALANCE 0LOC_CURRCY
Sales for the Period 0SALES 0LOC_CURRCY
Total credit postings 0CREDIT 0LOC_CURRCY
Total Debit Postings 0DEBIT 0LOC_CURRCY
4 Data Loading Strategy (Frequency, event chain)
The data will be loaded weekly.
5 Transfer rules
Standard Business Content Transfer rules will be enhanced with profit center and Business Area.
6 Update Rules (start routine, return table)
Standard Business Content Update rules will be enhanced with profit center and Business Area.
7 Virtual key figures / Characteristics
Not required.
8 Aggregates
Suitable aggregates if required will be created according to BW statistics proposals.
9 Enhancements, Gaps and Possible Approaches to Bridge the Gaps
Business Area and Profit Center are not present in the standard cube. The cube will be enhanced with the above-mentioned characteristics and to derive the values of the same. The exit will be used to enhance the data source 0FI_AR_6.
10 Assumptions / Prerequisites
11 Authorization and User Roles
Thanks,
Sankar M -
Hi SAPians,
We are a bunch of SAP trainees, and have recently completed a corporate training as a final year project.
We need to prepare documentation, report and presentation for project completion and degree.
we have all the screen shots, theory explanation about SAP and our related project, but we're not able to add them up.
Please provide us a template idea of what should be the contents of a project documentation should be, or if you could provide us info on how should the index looks like, that would be a great help.
ThanksSAP's tool for creating documentation is [Knowledge Warehouse|http://help.sap.com/saphelp_nw70ehp1/helpdata/en/8f/d82d37ba466b5be10000009b38f936/frameset.htm].
Hope this helps,
Rossen -
Documentation formats for interfaces, classes, abstract classes
I am writing docs and want to make sure it conforms to best practices. Here is what I am doing:
interfaces = [italics, not bold]
classes = [not italics, bold]
abstract classes = [italics, bold]
I am most unsure of abstract classes?
That is important to me, so please help me get this straight. thanks.Everybody knows that interfaces are blue, classes are red, and abstract classes use jumpy text.
(that was a joke by the way)
To my mind, using bold for abstract classes would be misleading. Just on an intuitive level, bold seems more concrete. But that's just me. I think the best thing to do is just to decorate the names with "<<interface>>" or "<<abstract>>" so there's no confusion. -
Date formats and etext templates
I have been working with etext templates in the last few days and am struggling with date conversion. My XML file has dates in the format DD-MON-YY and my output requires DDMMYYYY. It seems that the format conversion in etext template only works when the xml date is in the format YYYY-MM-DD. I thought I would convert the DD-MON-YY using a combination of TO_DATE and TO_CHAR but TO_CHAR doesn't seem to accept the date mask in etext templates. It looks like I will have to modify the original report unless someone has a way to achieve this in the template.
Thanks,
DaveI had to change the report. You may be able to change the setup in the reports server to alter the default date format but I didn't want to do that in case it affected the output of any of the other reports that are being run. (N.B. I haven't tried this myself so not sure it can be done).
The change to the report is pretty simple, I just added a formula column that took a copy of the standard column in the report and used to_char to reformat the date. In my case I reformatted to YYYY-MM-DD so that I could use the template to change the format to the required style. This is just in case there is a later change in the output style so I won't have to modify the report again.
When the date in the XML is in the format YYYY-MM-DD the documented formatting options work (e.g. "Date , DDMMYYYY" would convert "2005-10-26" to "26102005"). -
Documenting answers and dashboards
Is there any way of automatically generating documentation (e.g. for inclusion in technical/design specs) for answers requests and dashboards.
Given that answers metadata is stored as XML (in files under the BIData directory) I would have thought that some sort of tool would be available. I know that in the repository manager (admin tool) there is a metadata report option, but there does not seem to be antything equivalent for anwers and dashboards.
Thanks,
ChrisThanks Stijn,
It is a good start - and certainly lets me see/check the basis of the answers requests. However I was hoping that there would be some way of creating documentation (word/PDF etc).
As I said before, the answers requests seem to be stored as XML on disk, so I was hoping that there was a standard way of converting them to a documented format (e.g like javadoc for java programs)
Chris -
What format is IP SLA History "SampleT"
I am trying to use IP SLA on a CiscoIOS 12.4(24)T6 router.
It is configure to log failures only. However, we cannot interpet the output "SampleT". It shows a "SampleT" as in Start Time that is not in a recognized or documented format.
The documentation states that it is now in "milliseconds", but that does not make sense for an Absolute Time, only for a Duration Time.
http://www.cisco.com/en/US/docs/ios/ipsla/command/reference/sla_04.html#wp1133606
Here is the output:
aus-hym-rtr01#sh ip sla history
Point by point History
Entry = Entry number
LifeI = Life index
BucketI = Bucket index
SampleI = Sample index
SampleT = Sample start time
CompT = RTT (milliseconds)
Sense = Response return code
Entry LifeI BucketI SampleI SampleT CompT Sense TargetAddr
1 1 433 1 783584668 0 4 172.22.255.253
1 1 434 1 783585668 0 4 172.22.255.253
1 1 435 1 783586668 0 4 172.22.255.253
1 1 436 1 783587668 0 4 172.22.255.253
1 1 437 1 783588668 0 4 172.22.255.253
1 1 438 1 783589668 0 4 172.22.255.253
1 1 439 1 783590668 0 4 172.22.255.253
1 1 440 1 783591668 0 4 172.22.255.253
1 1 441 1 783592668 0 4 172.22.255.253
1 1 442 1 783593668 0 4 172.22.255.253
1 1 443 1 783594668 0 4 172.22.255.253
1 1 444 1 783595668 0 4 172.22.255.253
1 1 445 1 783596668 0 4 172.22.255.253
1 1 446 1 783597668 0 4 172.22.255.253
1 1 447 1 783598668 0 4 172.22.255.253
How can I convert the "SampleT" aka "Sample Start Time" to a Human Date/Time?
And even more frustrating, why can't I find this documented anywhere?
Thanks,
KrisThe SampleT timestamp is the SysUpTime value at the start of operation iteration. A documenation bug CSCua91554 has been filed to add this to the IP SLA command reference for the 'show ip sla history' command.
Thank you.
-Rahul -
May I suggest improving documentation somewhat:
Error at or near character 166 in the format string: Number of arguments exceed the maximum supported.
This type of error could be reduced by a more visible note in the documentation:
Formats the source1, . . . , sourcen arguments, where n < 30
(I know that this number is mentioned for the source parameter, but not for the function itself)
Thanks!
Solved!
Go to Solution.Thank you Wolfgang for your advice.
We are pleased to hear about your documentation improvement suggestion.
I created a CAR (Corrective Action Request) and forwarded it to our R&D Department in Austin, Texas, USA.
They will take care on this topic and will improve the documentation in future versions of LV CVI.
Regards
Christian -
How should NEF files from my D300 be dealt with?
I have a D300 and CS2. I have the CS2 version of Lightroom, PS and Bridge. I've been researching NEF files and their compatibility with the adobe applications I have. I'm confused on the best way to work with NEF files produced by the D300 directly with the versions of PS, Lr, and Br that I have. I hope I can work with the NEF files directly with the adobe products.
I've learned the following from what I've read. I think each version of Ps, Br, and Lr are very picky on which versions of NEFs they will support. This is due to the constant tweaking of the NEF format. The support for a certain NEF is dependent on when the version of Ps, Lr, and Br were released. In other words, there is only good support for the NEFs that are created by current cameras at the time of the release of the Adobe software. The new software doesn't support the older NEFs. And the older software doesn't support newer cameras.
I've also read that I can get around this by converting the NEFs to a DNG file. The articles I read were a little old, but there seemed to be some concern about whether the dng format would stay around for the future. I don't think it had gained a lot of acceptance.
Can someone please tell me the best way for me to work with RAW files in the adobe software that I have. Is there a plug in available for CS2 that will allow me to use the NEFs produced by my D300? Is my only option to convert these to DNGs before using them, if I want to keep my current version of Ps, Lr, and Br? If I convert them to DNG is the White Balance data available in Ps or Lr? Or, is the only other option to buy a more recent version of the adobe software? I don't plan to buy any new software now because I can't afford it. Even if I did, I'm concerned about backwards compatibility. Nikon considers the regular D300 as old. I don't think adobe does a good of supporting older camers in the newer software.
Can someone help me understand the best way to go about this. Thanks in advance for any help.All that changes in the NEF file between cameras is the usually camera name line. This is shown by using a Exif editor such as Exif tool and changing the camera name to one supported in the version of ACR used by your particualr version of LR or PS
When ever a new camera comes out Adobe profiles the sensor to produce a calibration file for use in LR and ACR, so if you just change the camera name you will be stuck with the old calibration data and colour reproduction may suffer. You can,of course, use Adobes free tool to produce your own calibrations.
Adobe updates ACR and LR around every three months to include calibration data for any camera released since the last update. These updates are free. However once LR or PS reaches a new full release these updates are no longer provided. You have a choice, when working with older software, of either updating to the new version, or using Adobes free DNG converter to convert the file to DNG. Nothing is lost in this process. All the original data is retained. Obviously whatever new things may be included in the latest versions of either ACR or LR will not work in the older versions. So if you use the DNG converter on a camera released since LR 3 came out you can use it in LR 2, but the lens correction tool will not work. Equally if you have LR 3, but only have CS 4 or older versions of PS, you will have to render the file in LR before PS can recognise the lens corrections applied.
You say that Adobe doesn't do a good job of supporting older cameras. This is strange. All older cameras are fully supported in LR and PS. Adobe have never dropped support for any camera and they also provide the DNG format which ensures both backward and forward compatibility with their software.
As far as acceptance of DNG as a container for RAW information from cameras not gaining acceptance, again a strange thing to say. Presently it is the only open and documented format available. It has been submitted to the ISO for acceptance as an international standard. It is also used natively by several major camera manufacturers, including Hassleblad, Leica and to some extent by Phase one. There really is presently no other format around. If the manufacturers wanted to get together to develop an alternative nothing is stooping them. Unfortunately the two big players in the market, Canon and Nikon, resist this and continue with their own propitiatory formats. Whilst these may be supported into the future it isn't guaranteed. However as DNG is a fully documented format there is no more reason to think it will stop being supported than any of the other standard formats (such as pdf, tiff and swf) developed by Adobe. -
i want to write a Document Management System to read the content of the MS Word file and convert it to the PDF file using java.
Does any java api can do this??
Thank YouThere are a number of solutions, none of which, unfortunately, are trivial:
In decreasing scale of difficulty:
a) Hand-code the entire solution. PDF and MS DOC are both well documented formats.
I wouldnt recommend you try this.
b) Use ready-made open source libraries:
Other than the ones mentioned earlier, there is an Apache Libraray (POI ?) which can be used for reading and writing streamed OLE objects (which is what a word doc is)
c) Use the Java-Activex bridge and use mature COM/Activex components
WinWord itself is an Activex component. There are loads of mature Activex components that can spew out PDF.
d) If platform is not an issue, use C# or VB.NET
I'll probably get flamed for this.
I am not a .NET advocate usually, but in this particular case you should be able to complete your task with least effort by using mature Activex libraries and one of the .NET languages. -
Elearning suite to Learning Management System (LMS) - how-to from an InDesign file?
We need to be able to export InDesign files to a portable SCORM format that could be loaded into various Learning Management Systems (LMS) – however, it is not obvious how we would do this? We need to publish our documents both in a book\PDF format and to various LMS systems such as Blackboard, Moodle, Angel, Desire2Learn, etc.
What am I trying to accomplish? Many of our College and University clients use Learning Management Systems (LMS). SCORM is a standardized interchange format used to provide internet ready information (e-book data, test questions, etc.) to any LMS systems. We need to export formatted InDesign documents – which for us are our Lab Manual (book) publications which include: text, graphics, pictures, etc.
Adobe advertises SCORM compatibility as part of its e-learning suite: http://help.adobe.com/en_US/elearningsuite/els/extensions/WSD40882CF-6 C5C-46c0-8D51-273830EB036B.html --- however, I cannot find anyone who can tell me how to get there from InDesign.
In addition, I find it very frustrating that after many calls to Adobe sales and technical staff that I can't find anyone who can help me with the details of how to get from InDesign to Adobe's "SCORM Packager" See: http://blogs.adobe.com/captivate/2009/01/scorm_packager.html which I believe is a part of the e-learning suite.
Is it possible to find a high level technical resource within Adobe that I could talk to who could help me with this issue --- we need to test the ability to produce SCORM compatible files from our InDesign files before we can make a purchase decision.Adobe's Multi SCORM Packaging tool is designed to take existing single SCORM packages (in zip file format) and merge them into a multi SCORM package with a rewritten imsmanifest.xml file at the root level to tell the LMS what the package contains. This allows the LMS to build the array of links that its SCORM player requires to allow the course user to navigate from one module to another.
So if InDesign is not currently capable of creating even a single SCO SCORM package, the Adobe Multi-SCORM Packaging tool is not going to be much use to you.
In reality, the Adobe tool is quite limited in functionality. It's more designed as an add-on for Captivate to allow multi-SCORM courses to be created. Your best bet would probably be to investigate other SCORM packaging tools such as RELOAD that allow you to take content created elsewhere and add them to a SCORM package as resources.
You may need to export your InDesign content as PDF files and have these set up as individual resources or assets in the SCORM package.
However, for any of this to work with an LMS is going to require the final package to have a SCORM API (done with JavaScript) so that user interaction with the individual components of the course is relayed back to the LMS via JavaScript variables. Packaging tools such as RELOAD may be able to do this with some types of content (e.g. HTML) but I don't know if InDesign output is going to be compatible with this approach.
Have you designed your InDesign course content with interactivity in mind, or is it just straight content delivered in a documentation format? -
HELP!!! Failed validation for emueration value which IS in the schema!
I am so troubled by this and hope someone can shed some light:
I have a schema which has StateCode element . We have all the states from "AL" to "WY" listed as enumeration values...but the xml instance failed to pass validation with "MO", which is part of the enumeration list.
Any one can think of any reasons? We are going live next week with this.
Thanks!
JasmineMike, here is the xsd...the table is created via DBMS_XMLSCHEMA.registerSchema:
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xdb="http://xmlns.oracle.com/xdb" elementFormDefault="qualified" attributeFormDefault="unqualified">
<xs:element name="BranchRegulatoryFiling" xdb:defaultTable="BRNCH_XML_STG_50">
<xs:complexType>
<xs:sequence>
<xs:element name="FileControl">
<xs:complexType>
<xs:attribute name="AsOfDate" type="xs:date" use="required"/>
<xs:attribute name="FileNumber" type="xs:int" use="required"/>
<xs:attribute name="FileTotal" type="xs:int" use="required"/>
<xs:attribute name="FirmCRDNumber" type="CRDNUM" use="required"/>
<xs:attribute name="SchVer" type="xs:double" use="required" fixed="5.0"/>
<xs:attribute name="TrackingNumber" type="xs:string" use="required"/>
</xs:complexType>
</xs:element>
<xs:element name="Branches" xdb:defaultTable="BRANCHES50">
<xs:complexType>
<xs:sequence>
<xs:element name="Branch" type="BranchType" maxOccurs="unbounded" xdb:defaultTable="BRANCH50"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:complexType name="BranchType">
<xs:sequence>
<xs:element name="LastAnnualInternalCompVisitDate" type="xs:date" default="1900-01-01">
<xs:annotation>
<xs:documentation>Ref # B3</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="Address" type="AddressType">
<xs:annotation>
<xs:documentation>Ref # B4</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="Supervisor" type="SupervisorType">
<xs:annotation>
<xs:documentation>Ref # B20</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="BranchStatistics" type="BranchStatisticsType"/>
</xs:sequence>
<xs:attributeGroup ref="BranchCodeAttributeGroup"/>
</xs:complexType>
<xs:complexType name="SupervisorType">
<xs:sequence>
<xs:element name="AsOfMonthEnd" type="AsOfMonth">
<xs:annotation>
<xs:documentation>Ref # B50</xs:documentation>
</xs:annotation>
</xs:element>
<xs:choice>
<xs:element name="PersonIncharge">
<xs:annotation>
<xs:documentation>Ref # B22</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:all>
<xs:element name="TotalComm" type="dollarAmount" minOccurs="0">
<xs:annotation>
<xs:documentation>Ref # B65</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="OffSiteSupervisor">
<xs:annotation>
<xs:documentation>Ref # B25</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:element name="TotalComm" type="dollarAmount" minOccurs="0">
<xs:annotation>
<xs:documentation>Ref # B65</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
<xs:attribute name="ProducingIndicator" type="YN" use="required">
<xs:annotation>
<xs:documentation>Ref # B26</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attributeGroup ref="RegisteredRepType"/>
<xs:attribute name="InternalProductionNumber" type="InternalProdNbr" use="required">
<xs:annotation>
<xs:documentation>Ref # B80</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:complexType>
</xs:element>
</xs:all>
<xs:attribute name="ProducingIndicator" type="YN" use="optional">
<xs:annotation>
<xs:documentation>Ref # B23</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attributeGroup ref="RegisteredRepType_optional"/>
<xs:attribute name="InternalProductionNumber" type="InternalProdNbr" use="required">
<xs:annotation>
<xs:documentation>Ref # B80</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:complexType>
</xs:element>
<xs:element name="OnSiteSupervisor">
<xs:annotation>
<xs:documentation>Ref # B28</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:attribute name="ProducingIndicator" type="YN" use="required">
<xs:annotation>
<xs:documentation>Ref # B29</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attributeGroup ref="RegisteredRepType"/>
<xs:attribute name="InternalProductionNumber" type="InternalProdNbr" use="required">
<xs:annotation>
<xs:documentation>Ref # B80</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:complexType>
</xs:element>
</xs:choice>
</xs:sequence>
</xs:complexType>
<xs:attributeGroup name="BranchCodeAttributeGroup">
<xs:attribute name="NYSEBranchCode" type="xs:string" use="required">
<xs:annotation>
<xs:documentation>Ref # B1</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:attributeGroup>
<xs:attributeGroup name="RegisteredRepType">
<xs:attribute name="RRLastName" type="xs:string" use="required">
<xs:annotation>
<xs:documentation>Ref # B14</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="RRFirstName" type="xs:string" use="required">
<xs:annotation>
<xs:documentation>Ref # B15</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="RRCRDNumber" type="CRDNUM" use="required">
<xs:annotation>
<xs:documentation>Ref # B16</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:attributeGroup>
<xs:attributeGroup name="RegisteredRepType_optional">
<xs:attribute name="RRLastName" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation>Ref # B14</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="RRFirstName" type="xs:string" use="optional">
<xs:annotation>
<xs:documentation>Ref # B15</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="RRCRDNumber" type="CRDNUM" use="optional">
<xs:annotation>
<xs:documentation>Ref # B16</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:attributeGroup>
<xs:attributeGroup name="FilingAttributeGroup">
<xs:attribute name="AsOfDate" type="xs:date"/>
<xs:attribute name="FirmCRDNumber" type="CRDNUM" use="required"/>
</xs:attributeGroup>
<xs:complexType name="BranchStatisticsType">
<xs:sequence>
<xs:element name="CurrentNumberOf90DayRestrictedAccounts" type="xs:nonNegativeInteger">
<xs:annotation>
<xs:documentation>Ref # B55</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="NumberOfIndependentContractors" type="xs:nonNegativeInteger">
<xs:annotation>
<xs:documentation>Ref # B56</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="TotalNumbersOfRRs" type="xs:nonNegativeInteger">
<xs:annotation>
<xs:documentation>Ref # B57</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="TotalNumberOfRRDiscretionaryAccounts" type="xs:nonNegativeInteger">
<xs:annotation>
<xs:documentation>Ref # B58</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="TotalAssetsUnderMgmt" type="positivedollarAmount">
<xs:annotation>
<xs:documentation>Ref # B59</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="ActiveAccounts">
<xs:annotation>
<xs:documentation>Ref # B60</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:element name="ActiveAccountsByMonth" minOccurs="3" maxOccurs="3">
<xs:complexType>
<xs:sequence>
<xs:element name="AsOfMonthEnd" type="AsOfMonth">
<xs:annotation>
<xs:documentation>Ref # B50</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="NumberOfActiveAccounts" type="xs:nonNegativeInteger">
<xs:annotation>
<xs:documentation>Ref # B61</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
<xs:attribute name="AvgNumberOfActiveAccounts" type="xs:nonNegativeInteger" use="required">
<xs:annotation>
<xs:documentation>Ref # B62</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:complexType>
</xs:element>
<xs:element name="GrossRevenues">
<xs:annotation>
<xs:documentation>Ref # B63</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:element name="GrossRevenueByMonth" minOccurs="12" maxOccurs="12">
<xs:complexType>
<xs:sequence>
<xs:element name="AsOfMonthEnd" type="AsOfMonth">
<xs:annotation>
<xs:documentation>Ref # B50</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="GrossRevenue" type="dollarAmount">
<xs:annotation>
<xs:documentation>Ref # B64</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
<xs:attribute name="TotalGrossRevenueForLast12Months" type="positivedollarAmount" use="required">
<xs:annotation>
<xs:documentation>Ref # B66</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:complexType>
</xs:element>
<xs:element name="TradeCorrections">
<xs:annotation>
<xs:documentation>Ref # B67</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:element name="TradeCorrectionsByMonth" minOccurs="3" maxOccurs="3">
<xs:complexType>
<xs:sequence>
<xs:element name="AsOfMonthEnd" type="AsOfMonth">
<xs:annotation>
<xs:documentation>Ref # B50</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="NumberOfTradeCorrections" type="xs:nonNegativeInteger">
<xs:annotation>
<xs:documentation>Ref # B68</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
<xs:attribute name="AvgNumberOfTradeCorrections" type="xs:nonNegativeInteger" use="required">
<xs:annotation>
<xs:documentation>Ref # B69</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:complexType>
</xs:element>
<xs:element name="RegTExtensions">
<xs:annotation>
<xs:documentation>Ref # B70</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:element name="RegTExtensionsByMonth" minOccurs="3" maxOccurs="3">
<xs:complexType>
<xs:sequence>
<xs:element name="AsOfMonthEnd" type="AsOfMonth">
<xs:annotation>
<xs:documentation>Ref # B50</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="NumberOfRegTExtensions" type="xs:nonNegativeInteger">
<xs:annotation>
<xs:documentation>Ref # B71</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
<xs:attribute name="AvgNumberOfRegTExtensions" type="xs:nonNegativeInteger" use="required">
<xs:annotation>
<xs:documentation>Ref # B72</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:complexType>
</xs:element>
<xs:element name="BouncedChecks" minOccurs="0">
<xs:annotation>
<xs:documentation>Ref # B73</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:element name="BouncedChecksByMonth" minOccurs="3" maxOccurs="3">
<xs:complexType>
<xs:all>
<xs:element name="AsOfMonthEnd" type="AsOfMonth">
<xs:annotation>
<xs:documentation>Ref # B50</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="TotalNumberOfBouncedChecks" type="xs:nonNegativeInteger">
<xs:annotation>
<xs:documentation>Ref # B74</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="TotalAmountOfBouncedChecks" type="positivedollarAmount">
<xs:annotation>
<xs:documentation>Ref # B74a</xs:documentation>
</xs:annotation>
</xs:element>
</xs:all>
</xs:complexType>
</xs:element>
</xs:sequence>
<xs:attribute name="AvgNumberOfBouncedChecks" type="xs:nonNegativeInteger" use="required">
<xs:annotation>
<xs:documentation>Ref # B75</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:complexType>
</xs:element>
<xs:element name="SSByFirm">
<xs:annotation>
<xs:documentation>Ref # B77</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:element name="SS" minOccurs="0" maxOccurs="unbounded">
<xs:complexType>
<xs:sequence>
<xs:element name="SSRegisteredRep" type="RegisteredRepType">
<xs:annotation>
<xs:documentation>Ref # B77</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="SSEffectiveDate" type="xs:date">
<xs:annotation>
<xs:documentation>Ref # B84</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="SSReason" type="xs:string">
<xs:annotation>
<xs:documentation>Ref # B85</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="RRCode" type="InternalProdNbr">
<xs:annotation>
<xs:documentation>Ref # B80</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
<xs:attribute name="TotalNumberOfSSbyFirm" type="xs:nonNegativeInteger" use="required">
<xs:annotation>
<xs:documentation>Ref # B78</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
<xs:complexType name="AddressType">
<xs:sequence>
<xs:element name="StreetAddress1">
<xs:annotation>
<xs:documentation>Ref # B4</xs:documentation>
</xs:annotation>
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:whiteSpace value="preserve"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="StreetAddress2" minOccurs="0">
<xs:annotation>
<xs:documentation>Ref # B5</xs:documentation>
</xs:annotation>
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:whiteSpace value="preserve"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="City">
<xs:annotation>
<xs:documentation>Ref # B6</xs:documentation>
</xs:annotation>
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:whiteSpace value="preserve"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="State">
<xs:annotation>
<xs:documentation>Ref # B7</xs:documentation>
</xs:annotation>
<xs:simpleType>
<xs:restriction base="stateCodeType">
<xs:whiteSpace value="collapse"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="Country">
<xs:annotation>
<xs:documentation>Ref # B8</xs:documentation>
</xs:annotation>
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:minLength value="2"/>
<xs:maxLength value="3"/>
<xs:whiteSpace value="collapse"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="ZipCode">
<xs:annotation>
<xs:documentation>Ref # B9</xs:documentation>
</xs:annotation>
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:whiteSpace value="collapse"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="IsBankLocation" type="YN" minOccurs="0">
<xs:annotation>
<xs:documentation>Ref # B4a</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:complexType>
<!-- Future use
<xs:complexType name="NameType">
<xs:attribute name="LastName" type="xs:string" use="required">
<xs:annotation>
<xs:documentation>Ref # BXX</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="FirstName" type="xs:string" use="required">
<xs:annotation>
<xs:documentation>Ref # BXX</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="CRDNumber" type="CRDNUM">
<xs:annotation>
<xs:documentation>Ref # BXX</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:complexType>
<xs:complexType name="TelephoneNumberType">
<xs:sequence>
<xs:element name="AreaCode" type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>Ref # Bxx</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="TelNumber" type="xs:string" minOccurs="0">
<xs:annotation>
<xs:documentation>Ref # Bxx</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:complexType>
<xs:complexType name="WebSiteAddressType">
<xs:sequence>
<xs:element name="WebSiteAddress" type="xs:string" minOccurs="0"/>
</xs:sequence>
</xs:complexType>-->
<xs:complexType name="RegisteredRepType">
<xs:attribute name="RRCRDNumber" type="CRDNUM" use="required">
<xs:annotation>
<xs:documentation>Ref # B81</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="RRLastName" type="xs:string">
<xs:annotation>
<xs:documentation>Ref # B82</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="RRFirstName" type="xs:string">
<xs:annotation>
<xs:documentation>Ref # B83</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:complexType>
<xs:simpleType name="stateCodeType">
<xs:restriction base="xs:string">
<xs:minLength value="2"/>
<xs:maxLength value="2"/>
<xs:enumeration value="AL"/>
<xs:enumeration value="AK"/>
<xs:enumeration value="AR"/>
<xs:enumeration value="AZ"/>
<xs:enumeration value="CA"/>
<xs:enumeration value="CO"/>
<xs:enumeration value="CT"/>
<xs:enumeration value="DC"/>
<xs:enumeration value="DE"/>
<xs:enumeration value="FL"/>
<xs:enumeration value="GA"/>
<xs:enumeration value="HI"/>
<xs:enumeration value="IA"/>
<xs:enumeration value="ID"/>
<xs:enumeration value="IL"/>
<xs:enumeration value="IN"/>
<xs:enumeration value="KS"/>
<xs:enumeration value="KY"/>
<xs:enumeration value="LA"/>
<xs:enumeration value="MA"/>
<xs:enumeration value="MD"/>
<xs:enumeration value="ME"/>
<xs:enumeration value="MI"/>
<xs:enumeration value="MN"/>
<xs:enumeration value="MO"/>
<xs:enumeration value="MS"/>
<xs:enumeration value="MT"/>
<xs:enumeration value="NC"/>
<xs:enumeration value="ND"/>
<xs:enumeration value="NE"/>
<xs:enumeration value="NH"/>
<xs:enumeration value="NJ"/>
<xs:enumeration value="NM"/>
<xs:enumeration value="NV"/>
<xs:enumeration value="NY"/>
<xs:enumeration value="OH"/>
<xs:enumeration value="OK"/>
<xs:enumeration value="OR"/>
<xs:enumeration value="PA"/>
<xs:enumeration value="PR"/>
<xs:enumeration value="RI"/>
<xs:enumeration value="SC"/>
<xs:enumeration value="SD"/>
<xs:enumeration value="TN"/>
<xs:enumeration value="TX"/>
<xs:enumeration value="UT"/>
<xs:enumeration value="VA"/>
<xs:enumeration value="VT"/>
<xs:enumeration value="WA"/>
<xs:enumeration value="WI"/>
<xs:enumeration value="WV"/>
<xs:enumeration value="WY"/>
<xs:enumeration value="AS"/>
<xs:enumeration value="VI"/>
<xs:enumeration value="PR"/>
<xs:enumeration value="AA"/>
<xs:enumeration value="AE"/>
<xs:enumeration value="AP"/>
<xs:enumeration value="FM"/>
<xs:enumeration value="GU"/>
<xs:enumeration value="MP"/>
<xs:enumeration value="PW"/>
<xs:enumeration value="CZ"/>
<xs:enumeration value="TT"/>
<xs:enumeration value="AB"/>
<xs:enumeration value="PQ"/>
<xs:enumeration value="SK"/>
<xs:enumeration value="ON"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="YN">
<xs:restriction base="xs:string">
<xs:enumeration value="Y"/>
<xs:enumeration value="N"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="dollarAmount">
<xs:restriction base="xs:long"/>
</xs:simpleType>
<xs:simpleType name="positivedollarAmount">
<xs:restriction base="xs:long">
<xs:minInclusive value="0"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="CRDNUM">
<xs:restriction base="xs:positiveInteger"/>
</xs:simpleType>
<xs:simpleType name="AsOfMonth">
<xs:annotation>
<xs:documentation>Format [YYYYMM]</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:length value="6"/>
<xs:pattern value="20[0-5][0-9][0-1][0-9]"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="InternalProdNbr">
<xs:restriction base="xs:string"/>
</xs:simpleType>
</xs:schema>
Maybe you are looking for
-
How can i delete all non native art?
Hello all, i have a pdf of a relatively complex architectural plan. I dont have acces to originals and i need to use that plan for some illustaive purposes. In the plan, I find a s**tload (over 2000) of non native art and they take a lot of cpu juice
-
Syncing iPod touch is like playing in the lottery
When I sync my iPod touch 4G, it'll begin its normal sync method of backing up, syncing contacts, ect... But more recently, it has been stumbling on backing up(which more or less I'll refer to as "syncing" for simplification here). It'll take about 5
-
Poor Service From Apple - Useless PowerBook
I've been having extraordinary problems with my PB these last few months. Being a college student and freelance photographer, my PB is very important in most aspects of my life. It is my primary computer so it is very difficult for me to parth with i
-
Enable the Number of Elements in the Array
once the Un-Initializing the array(1D or Multi) Placed ,we can not select the Number of element to Enable. byproviding the below option we can easily Enable the Elements in any array dimention.
-
Hello, experts! I have an WD application that uses EJB model. All works fine, but I want to change SAP JPA implementation to Hibernate JPA implementation. This is my persistence.xml <?xml version="1.0" encoding="UTF-8"?> <persistence version="1.0